Skip to main content
You can add external tools to Symbiotic Code using the Model Context Protocol, or MCP. Symbiotic Code supports both local and remote servers.
When you use an MCP server, it adds to the context. This can quickly add up if you have a lot of tools, as well as become a potential security liability. So we recommend being careful with which MCP servers you use.

Enable

You can define MCP servers in your configuration file under mcp. Add each MCP with a unique name. You can refer to that MCP by name when prompting the LLM.
symbiotic.jsonc
You can also disable a server by setting enabled to false. This is useful if you want to temporarily disable a server without removing it from your config.

Local

Add local MCP servers by setting type to "local" within the MCP object.
symbiotic.jsonc
The command is how the local MCP server is started. You can also pass in a list of environment variables as well. For example, here’s how you can add the test @modelcontextprotocol/server-everything MCP server.
symbiotic.jsonc
And to use it I can add use the mcp_everything tool to my prompts.

Options

Here are all the options for configuring a local MCP server.

Remote

Add remote MCP servers by setting type to "remote".
symbiotic.json
The url is the URL of the remote MCP server and with the headers option you can pass in a list of headers.

Options