Setup guide · MCP
Set up seenpaid in Grok
Grok is xAI’s assistant, at grok.com and through the xAI API. Grok cannot post for you on its own — not even to X. There are two real ways to give it seenpaid: a custom MCP connector in the Grok app, which you sign in to, or the xAI API’s remote MCP tool, where your own code passes the server and key on each request.
Card required, no charge until day 8. MCP access is on every plan.
- Endpoint
- api.seenpaid.com/mcp
- Transport
- Streamable HTTP
- Auth
- OAuth sign-in
- Tools
- 50
Four steps
How to connect Grok to seenpaid
No key to copy — you sign in to seenpaid instead.
- 1
Have your seenpaid account ready
No API key needed: Grok signs in to seenpaid with OAuth, and the sign-in decides which workspace it can act on. Start a trial first if you do not have an account.
- 2
Add seenpaid to Grok
Go to grok.com/connectors, click New Connector, choose Custom, and enter this URL. xAI’s docs say to “complete any required authentication”: seenpaid answers with its OAuth sign-in. xAI does not document a field for a static API key there, so we do not give one. On Grok Business and Enterprise, an admin has to provision the connector first.
Connector URLhttps://api.seenpaid.com/mcpChecked against the official docs: docs.x.ai/grok/connectors (custom MCP connectors at grok.com/connectors) · docs.x.ai/developers/tools/remote-mcp (type "mcp", server_url, server_label, headers). The API example uses headers rather than authorization because the docs do not say whether the latter adds the "Bearer " prefix seenpaid requires.
- 3
Restart and verify
Grok lists the tools it discovered on the connector. Ask it which seenpaid accounts are connected to confirm it can call them.
- 4
Ask for your first post
Start with “Which of my social accounts are connected?” — Grok calls list_accounts and names your channels. If none are connected yet, ask for a connect link: that one step needs you in a browser.
Another way
Building on the xAI API? Pass seenpaid as a remote MCP tool
The Responses API takes an "mcp" tool with server_url and server_label, plus headers for your server. The key goes in the Authorization header; your xAI key stays on the outer request.
$ curl https://api.x.ai/v1/responses \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $XAI_API_KEY" \
-d '{
"model": "grok-4.6",
"input": [{ "role": "user", "content": "Which of my social accounts are connected?" }],
"tools": [
{
"type": "mcp",
"server_url": "https://api.seenpaid.com/mcp",
"server_label": "seenpaid",
"headers": { "Authorization": "Bearer sp_your_api_key" }
}
]
}'Try asking
First things to ask Grok
Plain requests. Under each one, the seenpaid tools Grok calls to answer it.
Which of my social accounts are connected?
Callslist_accountsSchedule this post to X and LinkedIn for tomorrow at 9am.
Callsschedule_postWhat are the caption limits on X, Threads and Bluesky?
Callsget_platform_requirementsWhich platform earns the most per post?
Callsget_channel_roineeds revenue tracking
Revenue tracking is optional and off by default. Scheduling works without it. Every tool →
Troubleshooting
If it does not connect
401 Unauthorized
The request reached seenpaid but no valid credential came with it. Check the key starts with sp_, was not revoked, and is sent as “Authorization: Bearer sp_…” with the word Bearer and one space. seenpaid also answers 401 when the workspace has no active trial or plan, even with a correct key.
Wrong URL, or the server never connects
The endpoint is exactly https://api.seenpaid.com/mcp — not seenpaid.com, and not an /sse URL. seenpaid speaks Streamable HTTP only; a client set to SSE will not connect. Opening the URL in a browser shows a short explainer page, which is expected.
OAuth or API key — which one?
Config files and command-line clients send the sp_ key as a header. Connector screens in apps (claude.ai, Claude Desktop, ChatGPT, Grok) have no key field: they sign in to seenpaid with OAuth instead. Never paste your key into an OAuth client ID or secret field.
FAQ
Grok and seenpaid, answered
Not on its own — it has no credentials for your accounts. Connected to seenpaid’s MCP server it can schedule and publish to the 21 platforms seenpaid supports, and report back per platform what went out.
Go to grok.com/connectors, click New Connector, choose Custom, and enter this URL. xAI’s docs say to “complete any required authentication”: seenpaid answers with its OAuth sign-in. xAI does not document a field for a static API key there, so we do not give one. On Grok Business and Enterprise, an admin has to provision the connector first.
Use all 50 seenpaid tools: schedule, edit and cancel posts, check each platform’s limits before publishing, generate images and carousels, and read what published. Revenue tools (which post made money) work only if you switch on revenue tracking, which is optional and off by default.
No. MCP access is included on every seenpaid plan and in the 7-day trial.
It acts through a key or sign-in scoped to one seenpaid workspace; an API key can be revoked in Settings at any time. No tool returns your social passwords or platform tokens, and it cannot connect a new account on its own: it hands you a link and you sign in.
Also works with
Every other setup guide
Same server, same tools. Pick your client for its exact setup.