MCP-szerver

MCP-kliens beállítása

A kapcsolat két módja, a kész beállítási blokk helye, és a leggyakoribb csatlakozási hibák.

Setup steps

1
Create an MCP key
In Posty, open Settings → Developers. The key starts with psty_mcp_ and is only shown once, when you create it.
2
Copy the ready-to-use config block
The same page has ready-to-use blocks for the most common clients, with the key included.
3
Paste it into your client's settings
Each client stores its configuration in a different place, but the block contents are the same.
4
Restart the client
Most clients only load the configuration at startup.

Configuration format

Most clients use the same JSON structure. The URL and header are what matter:

{
  "mcpServers": {
    "posty": {
      "type": "http",
      "url": "https://api.posty.hu/mcp",
      "headers": {
        "Authorization": "Bearer psty_mcp_a_kulcsod"
      }
    }
  }
}

Use the Bearer prefix here

Send the MCP key with a Bearer prefix. For a REST API key, the header value is the key itself. These two cases are easy to mix up.

If your client uses OAuth and does not store a key, use https://api.posty.hu/mcp-oauth with no header. The client handles authorization itself.

Client-specific setup

Client	Where to configure it
Claude and Claude Code	In the client's MCP settings. A ready-to-use block is available under Settings → Developers.
ChatGPT	Under Connectors or in the app settings.
Gemini CLI	Under the `mcpServers` key in `~/.gemini/settings.json`, with the URL in the `httpUrl` field. The web and mobile Gemini apps cannot add a remote MCP server.
Other MCP client	Any client that supports streamable HTTP transport works with the format above.

The AI agents page has step-by-step instructions for each client, including terminal screenshots.

Check your setup

The easiest test is to ask your agent which channels you have. If it lists them, the connection and permissions are working.

If your client lists the available tools, you should see ten tools. The list is on the Tool reference page.

If it doesn't connect

Symptom	Cause	Fix
401 or “authentication failed”	You pasted a REST key instead of an MCP key.	Create a key that starts with `psty_mcp_` on the Settings → Developers page.
401 with the correct key	The `Bearer` prefix is missing.	The header value should be `Bearer psty_mcp_…`.
403, “not included in your plan”	MCP is available on the Pro plan or higher.	See the Plans page.
The server does not appear in the client	The client has not been restarted, or the configuration is in the wrong file.	Restart the client and check that the JSON is valid.
The agent does not see any channels	The key belongs to another workspace, or there are no connected channels.	Check the Channels page and verify which workspace the key was created in.

Is something missing from this page? Email [email protected] or use the form on the Help page.