No API key required. The Terminal49 MCP server supports OAuth 2.1. When you connect, Cursor opens a browser sign-in page — log in with your Terminal49 credentials and you’re done.
Add the server
1
Add the Terminal49 server
The fastest way is the one-click install button — it opens Cursor with the Terminal49 server configuration pre-filled; just confirm to install:
Alternatively, add the server manually to You can also add it from the UI: Cursor Settings → MCP → Add new MCP server, using the same URL.
.cursor/mcp.json in your project (or ~/.cursor/mcp.json to make it available in every project):2
Sign in to Terminal49
Cursor detects that the server requires authentication and shows a Needs login / Connect action next to it in Cursor Settings → MCP. Click it — your browser opens the Terminal49 sign-in page. Log in and approve access. Cursor stores and refreshes the tokens automatically.
3
Use it in a chat
Open the agent chat and ask:
“Using Terminal49, search for container CAIU1234567 and summarize its status.”
Alternative: install the Terminal49 plugin
Instead of adding the MCP server directly, you can install the Terminal49 plugin, which configures the same MCP connection and adds acontainer-tracking skill that teaches Cursor’s agent how to choose and sequence the Terminal49 tools. See the Agent plugins guide for install steps and details.
API key alternative
If you prefer a fixed credential (for example on a shared machine where the browser flow isn’t practical), create an API key in the developer portal and pass it as a header instead:Test your connection
Ask the Cursor agent:“List the tools available in the Terminal49 MCP server and what they’re for.”It should list tools such as
search_container, track_container, and get_container. See the tools reference for the full list, and Test Numbers for containers you can use during development.
Troubleshooting
Related guides
- Agent plugins – Terminal49 plugin with the
container-trackingskill - MCP Overview – Tools, prompts, and resources reference
- MCP Server Quickstart – Full setup, including API-key and local stdio options
- Other MCP clients – Generic configuration for any client