Connect Slack to Cursor

Generic HTTP

In any client that supports remote Streamable HTTP MCP and custom headers, add a remote MCP server using the values below. Get the complete key and team from OOMOL’s MCP setup page; field names and configuration formats vary by client.

URL

https://connector.oomol.com/v1/mcp

Transport

Streamable HTTP

Authorization

Bearer <mcp-api-key>

x-oo-team-name

<team-name>

Replace the placeholders with your own values. Send Authorization as Bearer followed by the MCP key, and x-oo-team-name as the team containing your connection. Prefer the client’s secret-input or environment-variable support. A URL-only setup without these headers is incomplete.

Verify the Connection

1. Reconnect the server in your client and check that it can list OOMOL tools such as connector_list_apps. If connection fails, check the URL and both authentication headers.
2. Run the read-only verification task in a new AI chat to check access to your resource and its data.

Cursor

Open ~/.cursor/mcp.json in your home folder. If it does not exist, create it with the JSON copied from OOMOL. Otherwise, merge the oomol entry into the existing mcpServers object. Save, reconnect the server, and start a new agent chat.

{
  "mcpServers": {
    "oomol": {
      "url": "https://connector.oomol.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer <mcp-api-key>",
        "x-oo-team-name": "<team-name>"
      }
    }
  }
}

Verify the Connection

1. Enable oomol in Cursor’s MCP settings and confirm that its tools load without an authentication error. Start a new Agent chat with the server enabled.
2. Run the read-only verification task in a new AI chat to check access to your resource and its data.

Codex

Open ~/.codex/config.toml and add or update the single oomol entry below. Replace <team-name> with the team in your copied OOMOL configuration. Set OOMOL_MCP_API_KEY in the environment of the process that launches Codex, using only the key from Authorization, without the Bearer prefix. Remove any old Authorization entry from oomol.http_headers and keep the key out of config.toml. Restart Codex with that environment.

[mcp_servers.oomol]
url = "https://connector.oomol.com/v1/mcp"
bearer_token_env_var = "OOMOL_MCP_API_KEY"

[mcp_servers.oomol.http_headers]
"x-oo-team-name" = "<team-name>"

For Codex CLI on macOS or Linux with Bash, run this command and paste the key at the hidden prompt. It passes the key to this Codex process without writing it to a file or shell history. A desktop or IDE client must receive the same variable in its own launch environment; a variable set in another terminal may not be available.

bash -c '
read -r -s -p "OOMOL MCP API key: " OOMOL_MCP_API_KEY || exit 1
export OOMOL_MCP_API_KEY
exec codex
'

Verify the Connection

1. In Codex CLI, use /mcp to check oomol. In a desktop or IDE client, check its MCP status. Confirm the process receives OOMOL_MCP_API_KEY, then start a new chat.
2. Run the read-only verification task in a new AI chat to check access to your resource and its data.

Claude Code

At your project root, create or merge .mcp.json with the configuration below and replace <team-name>. Set OOMOL_MCP_API_KEY in the environment that starts Claude Code, using the key without Bearer. The Bash example below prompts for it on macOS/Linux and starts claude. Approve the project server when prompted and use /mcp to check its status.

{
  "mcpServers": {
    "oomol": {
      "type": "http",
      "url": "https://connector.oomol.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${OOMOL_MCP_API_KEY}",
        "x-oo-team-name": "<team-name>"
      }
    }
  }
}

bash -c '
read -r -s -p "OOMOL MCP API key: " OOMOL_MCP_API_KEY || exit 1
export OOMOL_MCP_API_KEY
exec claude
'

Verify the Connection

1. In Claude Code, run /mcp and confirm oomol is connected. If authentication fails, check that the launch environment contains OOMOL_MCP_API_KEY. Start a new conversation.
2. Run the read-only verification task in a new AI chat to check access to your resource and its data.

VS Code / GitHub Copilot

In VS Code, run MCP: Open User Configuration and merge the servers and inputs entries below, preserving existing entries. Replace <team-name>, save, then use MCP: List Servers to start oomol. Enter the MCP key without Bearer when prompted. The password input keeps the key out of this configuration file.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "oomolMcpKey",
      "description": "OOMOL MCP API key",
      "password": true
    }
  ],
  "servers": {
    "oomol": {
      "type": "http",
      "url": "https://connector.oomol.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${input:oomolMcpKey}",
        "x-oo-team-name": "<team-name>"
      }
    }
  }
}

Verify the Connection

1. Run MCP: List Servers, confirm oomol is running, and make its tools available in your Copilot chat. If prompted again, provide the MCP key without Bearer.
2. Run the read-only verification task in a new AI chat to check access to your resource and its data.