Your own MCP server: give the crew tools only you have
Register your own MCP server under Customize → Connectors with a name and URL, or paste the mcpServers config you already use in Claude Desktop or Cursor. Attensira calls tools/list, and its agents can then call your tools in chats and automations as mcp__name__tool. Writes wait for your yes. Servers that sign in with OAuth cannot be called yet.
7 days free · card requiredHow the trial works
Asked: Which of our products are low on stock this week?
called mcp__warehouse__search
The agent called your server's own search tool by its namespaced name; the answer came from your warehouse, not from Attensira.
- Called as
- mcp__warehouse__search
- Writes
- wait for your yes
- A tool that changes something waits for approval.
- If the server is down
- mcp__warehouse__unavailable
- One tool that says the server cannot be reached.
The namespacing and the unavailable tool are as docs.attensira.com describes them; the server and the question are made up.
How do I register your own MCP server?
// paste what Claude Desktop or Cursor already uses
{
"mcpServers": {
"warehouse": {
"url": "https://mcp.example.com/mcp",
"headers": { "Authorization": "Bearer …" }
}
}
}
What can't the crew call yet?
- A server that runs as a local program, a command entry in your config, cannot be registered. There is nothing for Attensira to reach over the network.
- A server that signs in with OAuth can be registered but not called yet, because Attensira holds no OAuth token for it. The agent says it needs authorising; use a key, a header or an authenticating proxy instead.
- There is no button to re-read a server's tools on demand. Discovery runs when the server is added and when a session starts, within its time budget.
- Step 01
Add the server
Under Customize → Connectors, give it a name and its URL. Or paste an mcpServers configuration, and each remote server in it is imported with its URL and headers.
- Step 02
Give it what it signs in with
An open server needs nothing. Most servers that need a key expect it as a header such as Authorization Bearer, which comes across with a pasted configuration. Header values are write-only; the page shows which are set, never their values.
- Step 03
Let discovery run
Attensira calls tools/list on the server and registers what it finds. Discovery and calls are bounded by timeouts and a budget, so a server that is too slow is skipped for that session rather than delaying the answer.
- Step 04
Use it from a chat or an automation
The agents now call the server's tools like built-ins, in chats and in automations. A tool that writes stops and asks first, like every connector, unless the workspace is in Act for safe hygiene changes.
What do answer engines say about fixes that write back?
Perplexity on 4 Oct, asked for a tool that implements fixes: most monitor and suggest, and writing back to systems you own is rare. A registered server is one more system the crew can act in, and every write still waits for your yes.
Question: AI visibility tool that implements fixes automatically
Perplexity answered: An AI visibility tool that can automatically implement fixes exists in concept, but most tools today primarily monitor and suggest fixes rather than fully automate write-back changes across systems you don’t own. Some platforms offer automated artifact generation or CMS posting as part of automation, but true end-to-end auto-fix across all connected systems is rare and often limited.
Sources cited
- 1visibility.ai
- 2kime.ai
- 3zapier.com
- 4amplitude.com
- 5visible.seranking.com
- 6limy.ai
- +4 more
Not namedAttensira is missing from this Perplexity answer.
What can the crew do with your own MCP server?
- Give the crew data only you have, such as a product catalogue, a warehouse or an internal API, without waiting for Attensira to build a connector.
- Call the same tools from an automation on a schedule, not only when someone asks in a chat.
- Reuse the configuration you already have. A pasted mcpServers block brings each remote server's URL and headers across.
- Get a diagnosis instead of silence when your server is down. An unreachable server becomes one tool that says so when the agent calls it.
Why register your own MCP server?
Attensira's crew works from what it can read: your site, the answers engines give, your Search Console, the connectors you link. Some of what decides a good page lives somewhere only you can reach: a product catalogue, pricing rules, an internal API, a data warehouse. If you already run an MCP server in front of it, register it and the crew can call it like any built-in tool, in a chat or in an automation.
This is the inbound direction. Attensira's own MCP server is the opposite: it lets your assistant call Attensira. The two share no configuration and no credentials.
How do your tools appear to the crew?
Every discovered tool is namespaced as mcp__<slug>__<tool>: a search tool on a server registered as warehouse becomes mcp__warehouse__search, and Attensira's built-in tools, assembled first, can never be shadowed.
When your server is unreachable, it does not quietly vanish. It becomes one tool, mcp__<slug>__unavailable, that explains the problem when called. A missing tool looks to an agent like a capability that never existed, and it will confidently tell you it cannot do something it normally can; a tool that says "this server is unreachable" gets you a real diagnosis.
What should the first server be?
A read-only one: product data, pricing tables or docs the crew should quote from rather than guess. A connected server is available to the whole workspace, not to one person or one chat, so registering one is a workspace decision. Discovery runs when the server is added and when a session starts; there is no button to refresh its tool list on demand.
We show no live example on this page: our own workspaces have no registered server today, and we would rather show nothing than an invented one.
Questions about registering your own MCP server
How is this different from Attensira's own MCP server?
Can I paste the configuration I use in Claude Desktop or Cursor?
What happens if two servers both have a tool called search?
Can the crew write to my system without asking?
What if my server goes down?
Does my server work with OAuth?
Where do these facts come from?
Attensira's connectors documentation states that a pasted mcpServers configuration imports each remote server with its URL and headers, and that a local command entry cannot be registered.
docs.attensira.com · retrieved
“If you already use the server in Claude Desktop or Cursor, paste that
mcpServersconfiguration instead: each remote server in it is imported with its URL and its headers.”Attensira's connectors documentation states that a server whose auth mode is OAuth can be registered but the agent cannot call it yet, because Attensira holds no OAuth token for it.
docs.attensira.com · retrieved
“You can register a server whose auth mode is OAuth, but the agent cannot call it yet”
Attensira's connectors documentation states that discovered tools are namespaced as mcp__slug__tool and that built-ins cannot be shadowed because they are assembled first.
docs.attensira.com · retrieved
“Attensira's own built-in tools can never be shadowed by a registered one, because the built-ins are assembled first.”
Attensira's connectors documentation states that a server exceeding the discovery budget is skipped for that session rather than delaying the answer.
docs.attensira.com · retrieved
“A server that exceeds the discovery budget is skipped for that session rather than delaying the answer.”
Give the crew the tools only your server has.
7 days free · card requiredHow the trial works
Tell it where you want to be cited.
7 days free · card requiredHow the trial works
attensira.com's own workspace · read 4 Oct 2026 · n=4,518
197/ 4,518 answers4.4%