Custom Extensions

If an MCP server isn't in the registry, or you want to configure it yourself, add it as a custom extension.

Open Extensions from the account menu and click Add Custom.

Local Server (STDIO)Copy Anchor Link

A local server is a program AgentOne runs on your computer.

To add it:

1. Set Server Type to STDIO (Local).

2. Enter a Name, like Filesystem.

3. Enter the full Command to start the server, including its arguments. For example:

   Copy Text

   npx -y @modelcontextprotocol/server-filesystem ~/Documents

4. Add any Environment Variables the server needs, like API keys. Click Add for each one.

5. Optionally change Timeout (seconds) (default: 30).

6. Click Add Custom.

To have AgentOne ask before using this server's tools, turn on Require Approval By Default in the extension's Advanced settings after adding it. See Tool Approvals.

Remote Server (HTTP)Copy Anchor Link

A remote server is an MCP endpoint on the internet.

To add it:

1. Set Server Type to HTTP (Remote).
2. Enter a Name and the server's URL, like https://mcp.example.com/mcp.
3. If the server uses an API key, add it under HTTP Headers, for example Authorization with the value Bearer your-key.
4. Click Add Custom.

If the server supports OAuth sign-in, you can connect your account after adding it. See Signing In to an Extension.

Install from a LinkCopy Anchor Link

Some websites offer an Add to AgentOne link that starts with agent-one://mcp/install. Clicking one opens AgentOne with the Add Custom Extension form already filled in.

AgentOne shows Extension details were auto-filled so you know to check them. Review the command or URL carefully before clicking Add Custom. To create your own install links, see Deep Links.

Popular Servers to TryCopy Anchor Link

You can find many more on the MCP Registry or in Extensions.