Skip to content
Help centre

Cursor, Grok and other MCP clients

Connect Cursor, Grok or any MCP client that can send an Authorization header to a remote MCP server.

Any assistant that can connect to a remote MCP server over HTTP and send an Authorization header can use OpsDash. You need:

  • Server URL: your OpsDash's MCP address, shown in Settings › Agents (on opsdash.io, https://www.opsdash.io/api/mcp).
  • Header: Authorization: Bearer followed by a connection token.

OpsDash speaks MCP over streamable HTTP (protocol versions 2024-11-05, 2025-03-26 and 2025-06-18).

Cursor

Create a Cursor connection and choose Copy Cursor config, or add it by hand:

  1. In Cursor, open Settings › MCP and add a server named opsdash.
  2. Paste the configuration:
{
  "mcpServers": {
    "opsdash": {
      "url": "https://www.opsdash.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:OPSDASH_MCP_TOKEN}"
      }
    }
  }
}
  1. Set OPSDASH_MCP_TOKEN in the environment Cursor starts from (see Claude Code for how), then reload MCP.

You can also save this as .cursor/mcp.json in a project.

Grok

Create a Grok connection and copy its token. In Grok, add a custom MCP server at the MCP URL, with the header Authorization: Bearer and the token. Keep that connector: OpsDash tells Grok when the tool list changes, so you don't need a new token or to delete the connector to pick up new tools.

Assistants that only support sign-in (OAuth) connectors

Some assistants' "connector" settings only support signing in with OAuth, not a token in a header. OpsDash's MCP server uses tokens, so for those you need a bridge such as mcp-remote (as for Claude Desktop), if the assistant can run local MCP servers.

Check it works

Ask "Who am I in OpsDash?". The whoami tool replies with your workspace, the connection name, and how many open tasks are assigned to it.

These open in OpsDash. You’ll be asked to sign in first if you aren’t already.