Tellseed MCP server: setup and campaign workflow

Connect a hosted workspace

Start free, verify your email and open Connect in your workspace. Use the install link for Cursor or VS Code, or the copyable Claude Code command. The workspace supplies your own connection details, so you do not need to deploy a server or install Tellseed locally.

The MCP endpoint is https://app.tellseed.com/mcp. Authentication uses an Authorization bearer header containing your workspace owner key. An unauthenticated request returning 401 is expected; the public instructions are on this page.

Keep the key in your agent’s private connection settings. Do not put it in a campaign description, public link, chat transcript, screenshot or Git repository. Signing out of the browser does not revoke an installed agent. Use the explicit key replacement control if you need to invalidate the old key.

Choose a client that supports this connection

The workspace provides hosted setup options for Cursor, VS Code and Claude Code. Other MCP clients must support Streamable HTTP and a custom Authorization header. Check your client’s current configuration format instead of copying a different app’s configuration blindly.

Direct hosted Claude Desktop and ChatGPT connector flows are not implemented: Tellseed does not currently provide the OAuth discovery, consent and token exchange those flows need. A local stdio setup is a separate option for operators who already have source and database access.

MCP support is a client feature, not a model-size requirement. The agent needs to discover and call tools, follow their schemas and present the human approval step. Your AI provider’s usage charges are separate from Tellseed’s plan.

Use the campaign workflow

Start by asking the agent to check the workspace and list existing campaigns. Describe the audience, purpose, language, question format, branding and collection settings. Ask for ten questions shown one at a time if that is the experience you want.

The agent prepares a draft and returns preview and approval links. Inspect the preview, request changes and approve the finished version yourself in the browser. Then ask the agent to publish the approved version and return the contributor link.

Ask for the private answers view, statistics and export separately. Keep private access links out of public messages. In a new conversation, the agent should list campaigns instead of guessing an identifier or assuming the previous chat’s state.

Let the server describe its tools

The connected MCP server exposes tool descriptions and input schemas. These are the current interface contract. The agent should discover the available tools and read the returned status and errors instead of inventing tool names, links or successful actions.

For orientation, campaign_list finds campaigns in a fresh session and workspace_status reports workspace state. Campaign creation, draft updates, generation, approval status, publication and answer retrieval are part of the workflow. Approval remains a human step even when the agent handles the surrounding work.

Tellseed supports generated content and content you provide, free-text and classification tasks, branded contributor pages, configurable name and email collection, results and exports. Confirm the requested settings in the actual draft before publication.

If the agent cannot connect or publish

For a 401, check the endpoint and workspace key in the client settings. A browser login cookie is not the MCP key. A replaced key stops working, so update the installed connection after replacement.

If the agent cannot see tools, inspect the client’s MCP connection status and tool permissions. Reload the connection after changing its configuration. A model claiming it is connected is not evidence that the client discovered the tools.

If publication is refused, ask the agent for the current campaign status and the approval link. APPROVED and PUBLISHED are different states. If a change invalidates approval, review the updated draft and approve again. Do not ask the agent to bypass that gate.

If the contributor flow has the wrong length, ask the agent to check the generated item count and the number shown per round. If branding is missing, inspect the preview and supply a usable logo URL or exact colours. Contact Tellseed with the non-secret error message if the problem remains.