SiberMate

Remote MCP

MCP for Codex.

Connect the OpenAI Codex CLI to SiberMate by adding a remote MCP server in config.toml.

Markdown version Interactive MCP guide

Server URLs

Default remote MCP
https://mcp.sibermate.com/mcp
Multi-tenant profile
https://mcp.sibermate.com/profile/{YOUR TENANT DOMAIN}/mcp
Example profile
https://mcp.sibermate.com/profile/sibermate.com/mcp

Setup notes

  1. Edit ~/.codex/config.toml and add the [mcp_servers.sibermate] table below.
  2. Set SIBERMATE_API_KEY in your environment; Codex sends it as an Authorization: Bearer header.
  3. Some Codex builds require experimental_use_rmcp_client = true for HTTP servers. Use the domain profile URL for multiple tenants.

Authentication

  • Recommended remote flow: OAuth discovery from the MCP server URL.
  • Bearer fallback: send Authorization: Bearer <SIBERMATE_API_KEY> only when the client supports custom headers.
  • Local stdio fallback: run npx -y @sibermatedev/mcp with SIBERMATE_API_KEY in the client environment.

Codex config.toml

[mcp_servers.sibermate]
url = "https://mcp.sibermate.com/mcp"
bearer_token_env_var = "SIBERMATE_API_KEY"

Safety checklist

  • Use a dedicated tenant API key for MCP setup.
  • Keep API keys out of prompts, screenshots, repositories, browser history, and shared docs.
  • For profile URLs, the domain in the URL must match the tenant returned by the API key.
  • Review generated action plans before sending assignments, reminders, removals, uploads, or deletions.