Use the MCP server

Connect an MCP client to Mentortools with an API key. The Mentortools MCP server currently uses Bearer authentication, not OAuth. Your client must be able to send a custom HTTP header.

Before you start

1. Create a Mentortools API key under Settings → AI Interface and grant the permissions needed for your actions.
2. Use an MCP client that supports a custom Authorization header for HTTP connections, or a local bridge such as mcp-remote.

Use this exact URL, including the final slash: https://mcp.mentortools.com/mcp/. Omitting the slash can trigger a redirect that breaks the connection.

1. Create an API key

In Mentortools, open Settings → AI Interface → Add API key. Select the permissions, save, and copy the displayed key. Course read permission is enough for the first connection test. Keep the key private; do not paste it into chats or screenshots.

2. Enter the URL and authentication

Set the header name to Authorization. Its value must be exactly Bearer YOUR_API_TOKEN: capital B, one space, then the key. Replace only YOUR_API_TOKEN. Do not include angle brackets, quotes, or a second Bearer. Choose Bearer Token or Custom Header if your client offers an authentication setting; do not choose OAuth. If the client adds the Bearer prefix automatically, enter only the raw key in its token field.

These are the connection values; the surrounding configuration depends on your client:

{
  "type": "http",
  "url": "https://mcp.mentortools.com/mcp/",
  "headers": {
    "Authorization": "Bearer YOUR_API_TOKEN"
  }
}

3. Set up your client

Claude Code

Replace YOUR_API_TOKEN with your key:

claude mcp add-json mentortools-online '{
  "type": "http",
  "url": "https://mcp.mentortools.com/mcp/",
  "headers": {
    "Authorization": "Bearer YOUR_API_TOKEN"
  }
}'

Check with claude mcp list or /mcp in Claude Code.

Codex CLI

Set the environment variable in the terminal that launches Codex, then add the server to its configuration:

export MENTORTOOLS_API_TOKEN="YOUR_API_TOKEN"

~/.codex/config.toml:

[mcp_servers.mentortools-online]
url = "https://mcp.mentortools.com/mcp/"
bearer_token_env_var = "MENTORTOOLS_API_TOKEN"

Check with codex mcp list. Restart the Codex session after changing the configuration, with the environment variable still set.

Claude Desktop with a local bridge

Depending on the version, Claude Desktop may not send custom headers to a remote HTTP MCP server from its desktop configuration. Use mcp-remote as a local bridge in that case. Install Node.js and npx, add this to the Claude Desktop MCP configuration, and restart Claude Desktop:

{
  "mcpServers": {
    "mentortools-online": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.mentortools.com/mcp/",
        "--header",
        "Authorization: Bearer YOUR_API_TOKEN"
      ]
    }
  }
}

For other clients, use their HTTP MCP settings with the URL and header above. Do not copy one client's complete JSON format into another client.

Claude in the browser / Connectors

If setup asks for an OAuth login, OAuth Client ID, or Dynamic Client Registration, this Mentortools server cannot complete that flow yet. Use a client that can send a static Bearer header. Do not put an API key into OAuth Client ID or Secret fields.

4. Test the connection

Ask your agent to “List my available Mentortools courses.” First check that the server shows as connected. The tools you can use depend on your API key permissions. Not every Mentortools feature has an MCP tool yet; landing page management is not generally available.

Troubleshooting

• OAuth window or Client ID prompt: The client expects OAuth. Use Bearer token authentication or a client with custom headers.
• Immediate connection failure: Check that the URL is exactly https://mcp.mentortools.com/mcp/, including the final slash.
• 401 / unauthorized: Check the Authorization header, Bearer spelling, one space, and the valid key. In a token field that adds Bearer automatically, enter only the key.
• 403 or missing tool: Check the key's permissions. Some features do not yet have MCP tools.
• Still failing: Send support your client name, URL without token, time, and error message. Never send the API key.