# Your own MCP server: give the crew tools only you have > For the complete documentation index, see [llms.txt](https://attensira.com/llms.txt). > Every page on this site is also served as Markdown: append `.md` to any URL, or send `Accept: text/markdown`. > Register an MCP server you run under Customize → Connectors and Attensira's agents can call its tools in chats and automations, namespaced so nothing collides. - Canonical page: https://attensira.com/integrations/custom-mcp-server - Family: integrations - Last updated: 2026-10-05 - Author: Karl-Gustav Kallasmaa (https://x.com/kallasmaa) - Claims as data: https://attensira.com/claims.json?slug=custom-mcp-server **In short:** 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. ## 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. ## How do I register your own MCP server? 1. **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. 2. **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. 3. **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. 4. **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 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. ### 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____`: 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____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. ## FAQ ### How is this different from Attensira's own MCP server? They point in opposite directions. Your registered server is a tool the Attensira crew calls. Attensira's MCP server lets your assistant, such as Claude or ChatGPT, call Attensira. They share no configuration and no credentials. ### Can I paste the configuration I use in Claude Desktop or Cursor? Yes. Paste the mcpServers block and each remote server in it is imported with its URL and headers. Local command entries are skipped, because there is nothing to reach over the network. ### What happens if two servers both have a tool called search? Nothing collides. Each server's tools carry its own name, so the crew sees mcp__one__search and mcp__two__search as two different tools. ### Can the crew write to my system without asking? No. A tool call that writes stops and asks first, like every connector. The one standing yes is Act mode, which covers safe hygiene changes only, and anything that makes a claim still asks. ### What if my server goes down? It becomes a single tool named mcp__slug__unavailable that explains the problem when called, so the agent reports the outage instead of claiming the capability never existed. ### Does my server work with OAuth? Not yet. You can register it, but Attensira holds no OAuth token for it, so the agent cannot call it. Use an API key, a header, or an authenticating proxy in front of the server. ## Sources Each entry below is one claim on this page. `retrieved` is the date the exporter or a human last saw the source say this, and nothing more: it is not a publication date and not a promise of re-verification. `cite` is the anchor on the canonical page where this claim is rendered. ### plugins-paste-config 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. - source: https://docs.attensira.com/agent/plugins (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/custom-mcp-server#claim-plugins-paste-config > If you already use the server in Claude Desktop or Cursor, paste that `mcpServers` configuration instead: each remote server in it is imported with its URL and its headers. ### plugins-oauth-not-callable 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. - source: https://docs.attensira.com/agent/plugins (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/custom-mcp-server#claim-plugins-oauth-not-callable > You can register a server whose auth mode is OAuth, but the agent cannot call it yet ### plugins-namespacing 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. - source: https://docs.attensira.com/agent/plugins (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/custom-mcp-server#claim-plugins-namespacing > Attensira's own built-in tools can never be shadowed by a registered one, because the built-ins are assembled first. ### plugins-discovery-budget Attensira's connectors documentation states that a server exceeding the discovery budget is skipped for that session rather than delaying the answer. - source: https://docs.attensira.com/agent/plugins (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/custom-mcp-server#claim-plugins-discovery-budget > A server that exceeds the discovery budget is skipped for that session rather than delaying the answer.