MCP
Stackboard runs an MCP server your AI agent can connect to by URL. Once connected, an agent such as Claude, Claude Code, Cursor or VS Code can register and manage apps for you, with your permissions, and nothing to install.
https://app.stackboard.ai/mcpConnect
Section titled “Connect”Add the URL to your agent. The first time it connects, it opens Stackboard in your browser and asks you to approve it. Choose the organization it should work in, and select Connect.
Claude
Section titled “Claude”In Claude’s settings, add a custom connector and paste the URL.
Claude Code
Section titled “Claude Code”claude mcp add --transport http stackboard https://app.stackboard.ai/mcpThen run /mcp in Claude Code and choose stackboard to approve it.
Cursor, VS Code and others
Section titled “Cursor, VS Code and others”Add the server to the client’s MCP settings:
{ "mcpServers": { "stackboard": { "url": "https://app.stackboard.ai/mcp" } }}Some clients name the top-level key servers and ask for "type": "http"
beside the URL. Check your client’s documentation for its exact format.
Once connected, ask the agent which Stackboard account it is using. It should answer with your name and organization.
Clients without OAuth
Section titled “Clients without OAuth”If your agent cannot open a browser to approve a connection, give it a personal access token instead. Create one under Settings → Personal access tokens in Stackboard, then send it as a header:
{ "mcpServers": { "stackboard": { "url": "https://app.stackboard.ai/mcp", "headers": { "Authorization": "Bearer <your token>" } } }}For Claude Code:
claude mcp add --transport http stackboard https://app.stackboard.ai/mcp \ --header "Authorization: Bearer $STACKBOARD_TOKEN"| Tool | What it does |
|---|---|
stackboard_whoami |
Who you are connected as, and which organization it works in |
stackboard_list |
The apps you own, with their ids |
stackboard_validate |
Checks a repository can be read before registering it |
stackboard_register |
Registers a repository you have already pushed as an app |
stackboard_env_set |
Declares a variable, or sets a public one |
stackboard_target_add |
Allows an app to call an API host |
stackboard_share |
Changes who can open an app, and adds people or groups |
stackboard_cache_clear |
Clears an app’s cached API responses |
The tools follow the same rules as the CLI. If stackboard_register
answers with an app and a refused step, the app exists: fix that step rather
than registering again.
What an agent cannot do
Section titled “What an agent cannot do”Sign itself in. Connecting always takes a person approving it in a browser, or a token that person created.
Read or set secret values. An agent can declare a secret variable on an app, but you set its value yourself in Stackboard, under the app’s Variables settings. Secrets never pass through the agent.
Disconnect
Section titled “Disconnect”Every connected agent is listed under Settings → MCP connections, with the organization it works in and when it was last used. Select Disconnect to end one immediately.
For admins
Section titled “For admins”Org settings has an API access section listing every agent connected to the organization and every personal access token, with who made each one and when it was last used. Admins can disconnect an agent or revoke a token there without affecting anyone else.
MCP connections are on by default. Turning off Allow members to connect AI agents over MCP on the same page disconnects every agent in the organization at once and stops personal access tokens from being used over MCP. Turning it back on lets members connect again.
