Works with your agent

Noteheld works with any agent that can make an HTTP request or speak MCP. Speaking MCP means connecting to a remote MCP server over streamable HTTP and sending an Authorization: Bearer header, and making an HTTP request means calling the REST API with that same header or a GET of a read-only /k/<key> link.

Replace {origin} with https://itsme.tail24ad1e.ts.net and {key} with the whole key. Do not put the key in a repository. Do not give a remote connector a URL that contains the key.

The names below are products whose own documentation, read on 2026-10-15, shows one of those three doors. Each vendor sentence on this page has a source at the bottom. The source is that product's page and the date it was read.

Names are trademarks of their owners. Listing a name is not an endorsement or a partnership.

Three doors#

MCP#

POST {origin}/mcp with Authorization: Bearer {key}. Also send Content-Type: application/json and Accept: application/json, text/event-stream. GET and DELETE on /mcp return 405. Cookies are ignored on /mcp.

REST#

{origin}/api/v1/<tool> with the same Authorization header. GET and POST {origin}/api/v1/overview both return the overview.

Read-only link#

GET {origin}/k/{key} returns text/markdown: a short how-to, then the overview. The key sits in the path. That call does not write.

Find your agent#

Each name below is a product whose documentation showed a door. The second column is the door it uses.

CLI#

IDE#

Cloud and app builders#

Chat#

Frameworks#

Personal and automation#

Gemini CLI, Qwen Code, Grok Build, and Kimi Code are in the tables above. The chat apps with similar names are under Not yet, and so is Microsoft Copilot. GitHub Copilot, GitHub Copilot CLI, GitHub Copilot coding agent, and Microsoft Copilot Studio are in the tables above.

Connect it in one minute#

If your name has a heading below, copy that block. If it does not, use the generic shape, then match the field names under Things that trip people. Gemini CLI and Qwen Code need httpUrl, not url (34) (35). Names that connect by a shell, a request block, or a browser are under HTTP and the read-only link.

This is the generic shape. The key name is not url in every client.

{
  "url": "{origin}/mcp",
  "headers": {
    "Authorization": "Bearer {key}"
  }
}

OpenCode#

Config file opencode.json or opencode.jsonc, under mcp. A 401 starts a browser login unless oauth is false (1).

{
  "mcp": {
    "noteheld": {
      "type": "remote",
      "url": "{origin}/mcp",
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {key}"
      }
    }
  }
}

The captured sample that sets oauth to false uses Bearer {env:MY_API_KEY}. Another sample on the same page uses a literal bearer value. This block uses the literal and turns OAuth off.

Claude Code#

claude mcp add --transport http noteheld {origin}/mcp --header "Authorization: Bearer {key}"

User settings are ~/.claude.json. A .mcp.json at the repository root is a separate scope. Keep the key out of the repository. Do not run claude mcp get. From v2.1.265 the http transport tries streamable HTTP and can fall back to SSE (2).

Codex#

User file ~/.codex/config.toml. A .codex/config.toml in the repository is a second file. Keep secrets out of the repository. bearer_token_env_var is the name of an environment variable. Codex sends that value in Authorization. Set NOTEHELD_KEY to the key. The vendor sample's variable name was not copied here. The same page also documents http_headers for extra headers. You do not need that map for Noteheld (3).

[mcp_servers.noteheld]
url = "{origin}/mcp"
bearer_token_env_var = "NOTEHELD_KEY"

goose#

User file ~/.config/goose/config.yaml. On Windows the documented path is %APPDATA%\Block\goose\config\config.yaml. The type string is streamable_http and the address key is uri. SSE is not supported on that page. The captured sample leaves headers empty and uses https://example.com/mcp. Put the bearer header in that map (4).

extensions:
  noteheld:
    type: streamable_http
    name: noteheld
    enabled: true
    uri: "{origin}/mcp"
    headers:
      Authorization: "Bearer {key}"
    env_keys: []
    envs: {}
    timeout: 300

The one-shot command on that page takes a URL and does not take a header. Use the file when you need the header.

Cursor#

User file ~/.cursor/mcp.json. On Windows, %USERPROFILE%\.cursor\mcp.json. The same page also documents a file inside the repository. Keep the key in the user file. The captured sample server name is remote-server, the URL is https://api.example.com/mcp, and the header value is Bearer ${env:MY_SERVICE_TOKEN} (5).

{
  "mcpServers": {
    "noteheld": {
      "url": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MY_SERVICE_TOKEN}"
      }
    }
  }
}

Set MY_SERVICE_TOKEN to the key.

GitHub Copilot#

This is GitHub Copilot in the editor. The configuration reference used here is VS Code. Command: MCP: Add Server. The workspace file .vscode/mcp.json uses top-level servers. Do not commit that file. The header example on the reference is Bearer ${input:api-token}. When the editor asks, paste the key. type http is the streamable transport. The reference says VS Code tries HTTP first and can fall back to SSE (6).

{
  "servers": {
    "noteheld": {
      "type": "http",
      "url": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-token}"
      }
    }
  }
}

On Copilot Business and Copilot Enterprise, the policy "MCP servers in Copilot" is off until an admin enables it. Copilot Free, Pro, Pro+, and Max are outside that policy (7). A portable file ~/.copilot/mcp-config.json uses mcpServers. A repository-root .mcp.json does not expand VS Code input variables (6).

Devin Desktop#

Cascade config, macOS and Linux ~/.config/devin/mcp_config.json, Windows %APPDATA%\devin\mcp_config.json. The field is serverUrl. The captured sample uses the header name API_KEY and the value Bearer ${env:AUTH_TOKEN}. The headers object is free-form, so the name for Noteheld is Authorization. Set AUTH_TOKEN to the key (8).

{
  "mcpServers": {
    "noteheld": {
      "serverUrl": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer ${env:AUTH_TOKEN}"
      }
    }
  }
}

That page is the legacy Cascade agent. It says new tabs use Devin Local, which reads the Devin CLI config instead. The CLI page was not read in full. Enterprise must turn MCP on, and one allowlisted server blocks the rest (8).

Antigravity#

Global file ~/.gemini/config/mcp_config.json. That is not Gemini CLI's ~/.gemini/settings.json. The field is serverUrl. The page says the legacy keys url and httpUrl are unsupported. The captured URL is https://api.example.com/mcp/ and the sample value is Bearer YOUR_API_TOKEN (9).

{
  "mcpServers": {
    "noteheld": {
      "serverUrl": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer {key}"
      }
    }
  }
}

There is also a workspace file .agents/mcp_config.json. Keep the key in the global file.

Zed#

Open the settings file with zed: open settings file. The key is context_servers. If Authorization is missing, Zed starts OAuth. The captured URL is https://example.com/mcp and the sample value is Bearer <token> (10).

{
  "context_servers": {
    "noteheld": {
      "url": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer {key}"
      }
    }
  }
}

Cline#

CLI file ~/.cline/data/settings/cline_mcp_settings.json. If type is omitted, Cline uses legacy SSE. Set streamableHttp. The captured URL is https://example.com/mcp and the sample value is Bearer your-token (11).

{
  "mcpServers": {
    "noteheld": {
      "type": "streamableHttp",
      "url": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer {key}"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Devin#

Cloud path: Customize, then MCPs. Use Auth Header, not the page that tells other clients how to call Devin. That other page is Devin as a server at https://mcp.devin.ai/mcp (13). For Noteheld, Devin is the client. HTTP (Streamable HTTP) is what that client page recommends for new servers. The header key defaults to Authorization and the sample value is Bearer your-token (12).

{
  "transport": "HTTP",
  "url": "{origin}/mcp",
  "auth_method": "auth_header",
  "headers": {
    "Authorization": "Bearer {key}"
  }
}

The CLI surface falls back from HTTP to SSE on some 4xx responses, and not on 401 (12).

Replit Agent#

MCP Servers settings, Add MCP server, paste an HTTPS URL, then Advanced settings for headers. The install-link JSON uses an array of {key, value}, not a map. The captured URL is https://example.com/mcp (14). The connect page's example header name is X-API-Key (15). Replit also publishes its own server for other clients. That server is the other direction (16).

{
  "displayName": "Noteheld",
  "baseUrl": "{origin}/mcp",
  "headers": [
    {
      "key": "Authorization",
      "value": "Bearer {key}"
    }
  ]
}

Lovable#

Connectors, then MCP server. Choose Bearer token or API key. The page says that choice is for servers that do not support OAuth. It does not show the wire header name. Custom MCP is on for every plan until an admin turns it off. Direct connection does not need the Enterprise static-IP option. Lovable also exposes https://mcp.lovable.dev for other clients. That is the other direction (17).

Bolt#

Chat connectors, custom connector. Set transport to HTTP. Use SSE only when the server's documentation says to. Authentication is a single API key field or MCP OAuth. The page does not say the API key is sent as Authorization: Bearer. If it goes out under another name, Noteheld will reject it (18).

v0#

MCP menu, custom server, Bearer Token, and paste the key. You do not have to put Authorization in the custom-headers map when the auth kind is bearer. The pages read do not use the words streamable HTTP. Some sample URLs end in /sse. Use {origin}/mcp. A changelog entry says the API can connect to any custom MCP server (19) (20) (21).

Claude#

This is the chat app, Cowork, and Claude Desktop remote connectors. It is not Claude Code. Pro, Max, Team, and Enterprise: add a custom connector, then under Request headers add the credential. The builder authentication page says the value is sent exactly as you type it, so the value is Bearer {key} with the scheme included. A search extract of that page calls static headers a beta for a limited set of organizations, and says owners without access do not see Request headers. The help article shows those steps on Pro, Max, Team, and Enterprise. On the Free plan the help article allows one custom connector, and the numbered header steps are not in that section. Team and Enterprise: an Owner adds the connector (22) (23).

The connector runs on the public internet. A localhost or private URL will not connect. Authorization is dropped if the URL redirects to another host (22). The builder overview says to use Streamable HTTP, and that legacy HTTP+SSE is also supported (24).

LangChain#

In code, not a config file. Python: a URL is Streamable HTTP, and auth is the bearer string. The captured call uses the names url and token (26).

async with MCPAdapter(Client("{origin}/mcp", auth="{key}")) as adapter:
    return await adapter.list_tools()

JavaScript: transport http, and headers.Authorization. The captured URL is https://docs.langchain.com/mcp and the sample value is Bearer YOUR_TOKEN (25).

new MultiServerMCPClient({
  mcp: {
    transport: "http",
    url: "{origin}/mcp",
    headers: { Authorization: "Bearer {key}" }
  }
})

A client that only has a URL and then tries OAuth will not send this header (26).

OpenClaw#

Config mcp.servers. If transport is omitted on a URL, OpenClaw uses SSE. Set streamable-http. While auth is oauth, a static Authorization header is ignored. The captured URL is https://mcp.example.com/stream and the sample value is Bearer <token> (27).

{
  "mcp": {
    "servers": {
      "noteheld": {
        "url": "{origin}/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer {key}"
        }
      }
    }
  }
}

web_fetch is a GET that blocks private hostnames. A public read-only link can load through it. A localhost Noteheld URL cannot (28). exec can run curl.

Hermes Agent#

~/.hermes/config.yaml under mcp_servers. A url entry uses Streamable HTTP. The captured URL is https://mcp.example.com/mcp and the sample value is Bearer sk-... (29).

mcp_servers:
  noteheld:
    url: "{origin}/mcp"
    headers:
      Authorization: "Bearer {key}"

The terminal tool can also run the curl under Test it. hermes mcp serve is Hermes as a server. That is the other direction (29).

n8n#

In the workflow, add MCP Client or MCP Client Tool. Set the endpoint to {origin}/mcp, set Server Transport to HTTP Streamable, and choose Bearer or Multiple Headers. For Multiple Headers, the name is Authorization and the value is Bearer {key}. The client page lists Bearer, a generic header, multiple headers, and OAuth2 (30). An old MCP Client Tool node that only shows an SSE endpoint cannot talk to this server. Add the node fresh (31).

HTTP and the read-only link#

These names are on the list because the documentation shows a shell, a request block, or a browser. Do not paste the generic MCP shape into them.

**Aider.** There is no MCP page. /run runs a shell command. /web scrapes a URL and is not an authenticated call. Use /run with the curl under Test it, or /web for the read-only link (36).

**SWE-agent.** A maintainer wrote that MCP is not available (38). The agent runs a shell in a container. The architecture page does not promise outbound HTTPS. A normal local deployment can run curl (37). The docs also say the tool is maintenance-only and point people at mini-SWE-agent.

**Jules.** MCP on the changelog is a fixed list of partner servers. There is no documented way to add an arbitrary URL (39). Each task runs in a cloud VM with internet access, and the environment image includes curl, so the curl under Test it can call the REST API or GET the read-only link (40) (41).

**Browser Use.** The MCP client launches local stdio servers. The same page says it does not connect to HTTP or SSE endpoints. Add a custom action that sends the request, or open the read-only link in the browser (42).

**Skyvern.** The getting-started MCP page documents Skyvern as a server. A browser open of the read-only link can read the overview. A write path was not on that page (43).

**AutoGPT.** The blocks index lists Send Web Request and Send Authenticated Web Request. The header field names were not quoted, so use the curl shape from Test it inside that block if the block has a headers field (44).

**Make.** Use the HTTP app. It has a Headers field and GET. The MCP Client module's bearer field was not documented, so this page does not tell you to use that module (45).

**Activepieces.** The HTTP piece action Send HTTP request takes a method and optional authentication. That covers the REST call and a GET of the read-only link. The page does not paste the header field (46).

**Botpress.** The Simple HTTP request integration takes a URL, a method, and headers. The page says headers are often used for authentication and gives Authorization as the example. The exact bytes of that value were not shown (47).

**mini-SWE-agent.** Bash is the only tool. One action can be the curl under Test it. The shell does not keep environment variables between actions, so put the header on that command (48).

**Cody.** The page says remote MCP is unsupported and the config is a local command. The same page lists a terminal tool. It does not show curl. If that terminal can send HTTPS, use the curl under Test it (49).

Things that trip people#

Gemini CLI and Qwen Code, user settings or the add command. The captured sample URL is http://localhost:3000/mcp. Use your public {origin}/mcp when the client runs in the cloud (34) (35).

{
  "mcpServers": {
    "noteheld": {
      "httpUrl": "{origin}/mcp",
      "headers": {
        "Authorization": "Bearer {key}"
      }
    }
  }
}

GitHub Copilot coding agent. The captured sample is GitHub's own server. The header rule on that page is general: a $COPILOT_MCP_… name or a literal. Create the secret with that prefix, and set the value to Bearer {key} if you want the scheme in the secret (33).

{
  "mcpServers": {
    "noteheld": {
      "type": "http",
      "url": "{origin}/mcp",
      "headers": {
        "Authorization": "$COPILOT_MCP_NOTEHELD_KEY"
      }
    }
  }
}

Not yet#

These products are not in the tables above. Nothing here is a promise about a later release.

ChatGPT#

Custom MCP accepts OAuth, no authentication, or both. There is no field for a customer bearer header. The guide does not document a shell or a fetch that sets Authorization. Whether browsing can open a read-only link was not checked, so this page does not claim that either (50). Codex and the OpenAI Agents SDK are different products and are in the tables above.

Microsoft Copilot#

This is the Microsoft 365 Copilot connector, not GitHub Copilot and not Microsoft Copilot Studio. Those two are in the tables above. The admin connector uses a third-party identity provider, Microsoft Entra, or OAuth. The plugin authentication page says API key authentication is unsupported. The connector page describes read-only tools. No consumer screen for a custom URL was found, and no curl path was documented (51) (52).

Agentforce#

Streamable HTTP, and the documented auth is none or OAuth 2.0 client credentials. A static Authorization: Bearer header is not an option, and no generic fetch tool was found. A pasted read-only link is not documented as something the agent opens (53). Agentforce Vibes is a different product and is in the table below.

HuggingChat#

The user form is a name and a URL. Headers exist on the admin MCP_SERVERS entry, so an operator of a self-hosted Chat UI can set Authorization there. A user of the hosted chat cannot, on the page that was read (54).

Khoj#

The research-mode client speaks SSE or stdio. The stored API key is not passed into the SSE client. A bearer header is not sent. A read-only link was not shown as a tool (55).

SillyTavern#

The official docs have no MCP client and no agent HTTP tool. A third-party extension was not counted. The documented API connection is a model endpoint, not a call to Noteheld (56).

Qodo#

The IDE plugin page says the plugin is retired on 2026-10-30, so it is not in the list above. The prose says a remote MCP can take custom HTTP headers. The JSON sample did not render, so this page has no block to copy. Curl was not documented (57).

Firebase Studio#

The MCP page shows .idx/mcp.json with a headers field and Authorization: Bearer. The same page says signup is disabled as of 2026-06-22 and the product sunsets on 2027-03-22, so it is not in the list above. An existing workspace can still use that file until the sunset, and the workspace terminal can run curl (58).

Pages that do not show a bearer path#

Test it#

This call returns the overview when the key is good.

curl -sS \
  -H "Authorization: Bearer {key}" \
  {origin}/api/v1/overview

GET and POST both serve overview. You should see the overview map. An unknown, revoked, expired, or bad-checksum key returns one body, key_invalid. The same check over the read-only link is curl -sS {origin}/k/{key}.

Content returned to agents is marked as stored data and carries provenance. This does not stop a model from following text inside a note.

Open the quickstart

Sources#

1. OpenCode MCP servers. https://opencode.ai/docs/mcp-servers/ captured 2026-10-15.
2. Claude Code MCP. https://code.claude.com/docs/en/mcp captured 2026-10-15.
3. Codex MCP. https://developers.openai.com/codex/mcp captured 2026-10-15.
4. goose config files. https://goose-docs.ai/docs/guides/config-files captured 2026-10-15.
5. Cursor MCP. https://cursor.com/docs/mcp captured 2026-10-15.
6. VS Code MCP configuration reference. https://code.visualstudio.com/docs/copilot/reference/mcp-configuration captured 2026-10-15.
7. GitHub Copilot MCP policy. https://docs.github.com/en/copilot/customizing-copilot/using-model-context-protocol/extending-copilot-chat-with-mcp captured 2026-10-15.
8. Devin Desktop Cascade MCP. https://docs.devin.ai/desktop/cascade/mcp captured 2026-10-15.
9. Antigravity MCP. https://antigravity.google/docs/mcp/ captured 2026-10-15.
10. Zed MCP. https://zed.dev/docs/ai/mcp captured 2026-10-15.
11. Cline MCP overview. https://docs.cline.bot/mcp/mcp-overview captured 2026-10-15.
12. Devin MCP client. https://docs.devin.ai/work-with-devin/mcp captured 2026-10-15.
13. Devin as a server. https://docs.devin.ai/work-with-devin/devin-mcp captured 2026-10-15.
14. Replit MCP install links. https://docs.replit.com/references/mcp/install-links captured 2026-10-15.
15. Replit connect via MCP. https://docs.replit.com/build/connect-via-mcp captured 2026-10-15.
16. Replit MCP overview, Replit as a server. https://docs.replit.com/features/mcp/overview captured 2026-10-15.
17. Lovable custom MCP. https://docs.lovable.dev/integrations/custom-mcp captured 2026-10-15.
18. Bolt MCP. https://support.bolt.new/integrations/mcp captured 2026-10-15.
19. v0 MCP. https://v0.app/docs/MCP captured 2026-10-15.
20. v0 create MCP server. https://v0.app/docs/api/v1/reference/mcp-servers/create captured 2026-10-15.
21. v0 custom MCP changelog, published 2026-03-06. https://vercel.com/changelog/v0-api-now-supports-custom-mcp-servers captured 2026-10-15.
22. Claude custom connectors. https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp captured 2026-10-15.
23. Claude connector authentication, search extract. https://claude.com/docs/connectors/building/authentication captured 2026-10-15.
24. Claude connector building overview, search extract. https://claude.com/docs/connectors/building captured 2026-10-15.
25. LangChain JavaScript MCP. https://docs.langchain.com/oss/javascript/langchain/mcp-v1 captured 2026-10-15.
26. LangChain Python MCP auth. https://docs.langchain.com/oss/python/langchain/mcp/auth captured 2026-10-15.
27. OpenClaw MCP transports. https://docs.openclaw.ai/cli/mcp/transports captured 2026-10-15.
28. OpenClaw web fetch. https://docs.openclaw.ai/tools/web-fetch captured 2026-10-15.
29. Hermes Agent MCP. https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp captured 2026-10-15.
30. n8n MCP Client. https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcpclient captured 2026-10-15.
31. n8n MCP Client Tool transport. https://github.com/n8n-io/n8n/issues/35303 captured 2026-10-15.
32. Factory MCP. https://docs.factory.ai/harness/mcp captured 2026-10-15.
33. GitHub Copilot coding agent MCP. https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers captured 2026-10-15.
34. Gemini CLI MCP. https://geminicli.com/docs/tools/mcp-server/ captured 2026-10-15.
35. Qwen Code MCP. https://qwenlm.github.io/qwen-code-docs/en/users/features/mcp/ captured 2026-10-15.
36. Aider commands. https://aider.chat/docs/usage/commands.html captured 2026-10-15.
37. SWE-agent architecture. https://swe-agent.com/latest/background/architecture/ captured 2026-10-15.
38. SWE-agent MCP request. https://github.com/SWE-agent/SWE-agent/issues/861 captured 2026-10-15.
39. Jules MCP changelog. https://jules.google/docs/changelog/2026-02-02/ captured 2026-10-15.
40. Jules FAQ. https://jules.google/docs/faq/ captured 2026-10-15.
41. Jules environment. https://jules.google/docs/environment/ captured 2026-10-15.
42. Browser Use tools. https://docs.browser-use.com/open-source/customize/tools/add captured 2026-10-15.
43. Skyvern MCP. https://www.skyvern.com/docs/developers/getting-started/mcp captured 2026-10-15.
44. AutoGPT integrations. https://agpt.co/docs/integrations captured 2026-10-15.
45. Make HTTP app. https://apps.make.com/http captured 2026-10-15.
46. Activepieces HTTP. https://www.activepieces.com/pieces/http captured 2026-10-15.
47. Botpress HTTP request. https://botpress.com/integrations/http-request captured 2026-10-15.
48. mini-SWE-agent FAQ. https://mini-swe-agent.com/latest/faq/ captured 2026-10-15.
49. Cody agentic context. https://sourcegraph.com/docs/cody/capabilities/agentic-context-fetching captured 2026-10-15.
50. ChatGPT custom MCP. https://developers.openai.com/api/docs/guides/custom-mcp-server captured 2026-10-15.
51. Microsoft 365 Copilot custom connector, search extract. https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/set-up-custom-federated-connectors captured 2026-10-15.
52. Microsoft 365 Copilot plugin authentication, search extract. https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-authentication captured 2026-10-15.
53. Agentforce MCP considerations. https://help.salesforce.com/s/articleView?id=ai.agent_mcp_considerations.htm&language=en_US&type=5 captured 2026-10-15.
54. Hugging Face Chat UI MCP, search extract. https://huggingface.co/docs/chat-ui/en/configuration/mcp-tools captured 2026-10-15.
55. Khoj MCP client. https://github.com/khoj-ai/khoj/blob/master/src/khoj/processor/tools/mcp.py captured 2026-10-15.
56. SillyTavern API connections. https://docs.sillytavern.app/usage/api-connections/openai/ captured 2026-10-15.
57. Qodo agentic tools. https://docs.qodo.ai/qodo-ide/tools-mcps/agentic-tools-mcps captured 2026-10-15.
58. Firebase Studio MCP servers. https://firebase.google.com/docs/studio/mcp-servers captured 2026-10-15.
59. JetBrains AI Assistant MCP. https://www.jetbrains.com/help/ai-assistant/mcp.html captured 2026-10-15.
60. Trae MCP servers. https://docs.trae.ai/ide/add-mcp-servers captured 2026-10-15.
61. Continue MCP. https://docs.continue.dev/customize/deep-dives/mcp captured 2026-10-15.
62. GitLab Duo MCP clients. https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_clients/ captured 2026-10-15.
63. Void MCP issue, search extract. https://github.com/voideditor/void/issues/945 captured 2026-10-15.
64. avante.nvim repository. No configuration page found, 2026-10-15. https://github.com/yetone/avante.nvim captured 2026-10-15.
65. codecompanion.nvim homepage, search extract. https://codecompanion.olimorris.dev/ captured 2026-10-15.
66. Zencoder. https://zencoder.ai captured 2026-10-15.
67. gptel repository, README not fetched. https://github.com/karthink/gptel captured 2026-10-15.
68. Poolside. https://poolside.ai captured 2026-10-15.
69. Agentforce Vibes MCP servers. https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-mcp-servers.html captured 2026-10-15.
70. Stitch MCP setup, title only. https://stitch.withgoogle.com/docs/mcp/setup captured 2026-10-15.
71. Gemini custom apps. https://support.google.com/gemini/answer/17209137?hl=en captured 2026-10-15.
72. Grok connectors. https://docs.x.ai/grok/connectors captured 2026-10-15.
73. Perplexity custom remote connectors, search extract, full fetch timed out. https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors captured 2026-10-15.
74. Le Chat connectors announcement, search extract. https://mistral.ai/news/le-chat-mcp-connectors-memories/ captured 2026-10-15.
75. Kimi. https://www.kimi.com captured 2026-10-15.
76. DeepSeek. https://chat.deepseek.com captured 2026-10-15.
77. Qwen chat. https://chat.qwen.ai captured 2026-10-15.
78. Meta AI. https://meta.ai captured 2026-10-15.
79. Poe. https://poe.com captured 2026-10-15.
80. Doubao. https://www.doubao.com captured 2026-10-15.
81. Phind. https://www.phind.com captured 2026-10-15.
82. You.com as a server, search extract. https://you.com/docs/build-with-agents/mcp-server captured 2026-10-15.
83. Eliza plugin README, empty. https://github.com/elizaOS/eliza/blob/develop/plugins/plugin-mcp/README.md captured 2026-10-15.
84. FastGPT MCP server guide. https://doc.fastgpt.io/en/guide/build/publish/mcp_server captured 2026-10-15.
85. Coze MCP. https://docs.coze.cn/mcp captured 2026-10-15.
86. IronClaw MCP. https://docs.ironclaw.com/capabilities/mcp captured 2026-10-15.