Connect MCP and copy a setup prompt

Connect a compatible agent once, then use it to read data and configure Signailist. The MCP endpoint is https://api.signailist.com/mcp. The transport is Streamable HTTP and authentication is OAuth. An API key is for REST; it is not an MCP OAuth token.

Choose your client

Codex · Claude Code · Claude Desktop / web · Cursor · VS Code / Copilot

Connect Codex

Run this in your Codex terminal. The command adds a persistent entry named signailist to the user's shared Codex configuration and starts authorization:

codex mcp add signailist --url https://api.signailist.com/mcp --oauth-client-registration dcr

If the entry already exists, inspect it with codex mcp get signailist instead of adding a second one. To finish or renew an incomplete login:

codex mcp login signailist --oauth-client-registration dcr

Sign in as a workspace owner. Choose the intended workspace before allowing access; an already open test workspace is not necessarily the workspace you want. Select permissions and press Allow access yourself. A client cannot select another workspace through tool arguments after connection. Connect again if you need a separate grant for a different workspace.

Codex shares MCP configuration between supported clients on the same host. Use a new conversation after setup if the current conversation has not refreshed its tool catalog. Verify the URL and the actual connection by asking the agent to call capabilities, get_integration, and budget; a saved configuration alone does not prove authorization. Official Codex configuration documentation.

Choose permissions

Goal	Permissions
Inspect saved results and costs	read, billing:read
Prepare sources, topics, templates and a paused schedule	Add configure
Collect sources, run AI and upload assets	Add run
Supply materials from your system	Add ingest
Approve/publish and enable a recurring publication schedule	Add publish
Create subscriptions and inspect webhook delivery	Add webhooks

Publication starts unchecked. run does not permit enabling a publication schedule: that action requires publish, including schedules that prepare a candidate for approval. Creating a schedule leaves it disabled. Pausing a source and pausing a schedule are separate actions.

Only the owner changes daily limits in Integrations → API, MCP and webhooks. The agent can inspect its budget but cannot increase it. Top-ups are manual through the administrator. Connecting a Telegram account, provider sign-in and granting OAuth permissions can require the owner to use a browser.

Copy a prompt to connect Codex

Copy this entire block into your agent. It includes the documentation entry points and asks for a real read-only verification after authorization.

Connect Signailist MCP to my Codex.
Read https://docs.signailist.com/llms.txt and
https://docs.signailist.com/developers-mcp first.
The complete product/API documentation is https://docs.signailist.com/llms-full.txt;
the machine API contract is https://docs.signailist.com/openapi.json.

Inspect existing MCP settings. Reuse the signailist entry if it points to
https://api.signailist.com/mcp; do not overwrite another connection or expose tokens.
For an installed Codex CLI use:
codex mcp add signailist --url https://api.signailist.com/mcp --oauth-client-registration dcr
If already configured, use codex mcp login signailist --oauth-client-registration dcr.

Let me choose the workspace and grant OAuth access in the browser.
For a first setup suggest read, configure and billing:read; explain that run is
needed for paid work and publish is needed to enable recurring publication.
Do not create or enlarge permissions or a financial limit on my behalf.
After login call capabilities, get_integration and budget through the actual
MCP connection. Report the workspace, granted scopes and available balance.
Do not collect, generate, publish or enable schedules during this connection check.
If tools are unavailable in this conversation, explain how to refresh the client
or start a new conversation; do not pretend the connection was verified.

Claude Code

Add Signailist for your user, across projects:

claude mcp add --transport http --scope user signailist https://api.signailist.com/mcp

If already configured, inspect it with claude mcp get signailist. Start Claude Code, open /mcp, select Signailist and authenticate. Choose your workspace and permissions in the browser. Then use the verification prompt below. Claude Code MCP documentation.

Claude Desktop and Claude on the web

Open Customize → Connectors → Add → Custom → Web. Name the connector Signailist, enter https://api.signailist.com/mcp, and continue. Select OAuth sign-in; if offered an OAuth client choice, use Register automatically for Signailist's dynamic registration. Complete browser consent, then enable the connector in your chat. Organization policy can restrict adding connectors. Use the remote connector flow rather than putting this URL in a local stdio configuration. Claude connector documentation.

Cursor

Merge this entry into ~/.cursor/mcp.json for personal use, or .cursor/mcp.json for this project; preserve other servers:

{
  "mcpServers": {
    "signailist": {
      "url": "https://api.signailist.com/mcp"
    }
  }
}

Open Cursor's MCP settings in Customize, connect Signailist and complete OAuth. Enable its tools in Agent chat. No fixed Authorization header is needed. Cursor MCP documentation.

VS Code with GitHub Copilot

Run MCP: Add Server in the Command Palette. Choose HTTP, enter https://api.signailist.com/mcp and name it signailist. Choose the destination for your chat's agent harness; use Copilot Global if offered for personal Copilot configuration. Complete sign-in and enable tools in chat.

For the VS Code configuration format, merge into .vscode/mcp.json:

{
  "servers": {
    "signailist": {
      "type": "http",
      "url": "https://api.signailist.com/mcp"
    }
  }
}

This servers format differs from Cursor's mcpServers. Copilot harness configurations can differ too; prefer the guided flow for the selected harness. VS Code MCP reference.

Copy a prompt for any client

Use this in Claude Code, Claude Desktop, Cursor or Copilot. An agent without settings access will guide you through the steps above. Once connected, the weekly digest and other workflow prompts work with the same Signailist tools in each client.

Help connect Signailist MCP in [Claude Code / Claude Desktop / Cursor / VS Code Copilot].
Read https://docs.signailist.com/llms.txt and
https://docs.signailist.com/developers-mcp.
Complete documentation: https://docs.signailist.com/llms-full.txt.
API contract: https://docs.signailist.com/openapi.json.

Use https://api.signailist.com/mcp with Streamable HTTP and OAuth.
Follow the instructions for my client, not a configuration copied from another one.
Inspect existing settings; preserve other servers and reuse an existing Signailist
connection. If you cannot edit settings, give me the exact manual steps.
Do not ask for API keys, tokens or passwords in chat.
Let me select the workspace and permissions in the browser. For setup suggest
read, configure and billing:read; explain run and publish separately.
After connection, call capabilities, get_integration and budget using Signailist MCP.
Show the workspace, scopes and available balance. Do not collect, generate,
publish, enable schedules or raise limits during this connection check.
If tools are missing, help enable the connector or refresh the chat's tool list.

Disconnect and troubleshoot

• No tools: check the saved endpoint, complete OAuth, then refresh the client catalog. An SDK test or a configuration entry is not a successful client connection.
• Wrong workspace: reconnect and choose the intended workspace. Editing workspaceId in a tool body is rejected.
• 403: inspect get_integration and capabilities; request a new owner-approved grant if a required scope is absent. A role downgrade or revocation is enforced on queued work too.
• 402: inspect budget, reservations and daily limits. Retry only after resolving the budget condition, preserving the original operation's idempotency key when appropriate.
• Provider disconnected: use the provider connection step in Telegram or delivery, then check readiness again.
• Revoke a connection in Signailist integration settings. codex mcp logout signailist removes the local saved grant; codex mcp remove signailist removes its configuration. Use server-side revocation when stopping access, not just a local configuration edit.

Continue with the copyable workflow prompts or the complete API/tool catalog.