SpringBrand MCP Server: Setup and Tools
Connect SpringBrand to Claude Code, Codex, Cursor and any MCP-capable agent host.
Updated
The SpringBrand MCP server exposes SpringBrand tools to any MCP-capable AI agent. It ships inside the SpringBrand plugin, so installing the plugin also registers the server; you then complete an OAuth sign-in and the agent can discover tools, read their input schemas, run them and fetch saved results in the same conversation.
Install the MCP server
The MCP server is bundled with the SpringBrand plugin, so installing the plugin registers the server automatically. Paste the first instruction into your agent to install or update it, then complete the OAuth sign-in. Command-line hosts use the login commands below, while desktop apps show the same prompt in their plugin settings.
Any AI agent
Install or update SpringBrand: https://plugin.springbrand.ai/INSTALL.mdSign in (Claude Code CLI)
claude mcp login plugin:springbrand:springbrandSign in (Codex CLI)
codex mcp login springbrandDesktop hosts show the sign-in prompt in their plugin settings. Per-host steps: install guides.
How the SpringBrand MCP server works
The SpringBrand MCP server follows a discover-then-run pattern. Your agent first searches the catalog for an operation that matches the task, reads that operation's input contract, then runs it and reads the result. Discovery and schema lookups never execute anything, so the agent can explore safely before it commits to a run.
Authentication and accounts
The server uses OAuth, so you never paste an API key into your agent. Signing in once links the agent to your SpringBrand account, and some operations also ask you to connect a third-party account the first time you use them. The agent reports which connection is missing and guides you through adding it.
SpringBrand MCP tools
The SpringBrand MCP server exposes five tools that cover the whole run cycle. search_tools finds operations that match a task, get_tool_schemas reads an operation's input and output contract, execute_tools runs it, get_execution returns the status and saved result, and manage_connections links the third-party accounts an operation needs. Your agent picks among them while you describe the task in plain language.
| Tool | What it does |
|---|---|
| search_tools | Find operations that match a task description |
| get_tool_schemas | Read the input and output contract of an operation |
| execute_tools | Run one or more operations |
| get_execution | Read the status and saved result of a run |
| manage_connections | List and connect the third-party accounts an operation needs |
Tool names as exposed by the SpringBrand MCP server; your agent may prefix them with the server name.
SpringBrand MCP server FAQ
These answers cover what people ask most before connecting the SpringBrand MCP server: which agent hosts support it, whether you need an API key, and how updates work. In short, any MCP-capable host works, sign-in uses OAuth in your browser rather than a key you have to store, and pasting the install prompt again updates the plugin together with its bundled server.
Which agents can use the SpringBrand MCP server?
Any agent host that supports MCP plugins or servers. SpringBrand maintains step-by-step guides for Claude Code, Codex, Cursor and WorkBuddy on the install guides page.
Do I need an API key for the MCP server?
No. The MCP server signs in with OAuth in your browser, so there is no key to copy or rotate inside your agent.
How do I update the MCP server?
Paste the install prompt again. It updates the plugin, and the bundled MCP server updates with it.
SpringBrand developer docs
SpringBrand's developer documentation is split by how you connect. Start with the overview or the quickstart for a first working task, read the MCP server guide for how agents discover and run tools, the CLI quickstart for Claude Code CLI and Codex CLI, the API platform page for access paths and API keys, and the install guides for every supported agent host.