Skip to main content

Platform MCP

Platform MCP is a remote MCP server provided by Guppycubed. After a user authorizes it, an external AI client (Claude, ChatGPT, Cursor, Claude Code, Codex, and others) can read workspace data and create drafts and tasks within the authorized scope.

Endpoint​

ItemValue
MCP endpointhttps://mcp.guppycubed.com/mcp
TransportStreamable HTTP
AuthorizationOAuth 2.1 Authorization Code + PKCE (S256)
Client registrationDynamic Client Registration (DCR) supported
Protected resource metadata/.well-known/oauth-protected-resource/mcp
Authorization server metadata/.well-known/oauth-authorization-server/api/platform-mcp/oauth

The endpoint does not redirect; connect directly to the URL above.

Connection flow​

  1. In your MCP client, add a remote MCP server using the endpoint above.
  2. The client registers itself through DCR and opens the authorization page.
  3. Sign in with your Guppycubed account, choose the workspace and scopes to grant, and confirm.
  4. Once the client holds an access token, it can call tools.

Authorized connections can be reviewed and revoked under Settings → Connections (/portal/settings/connections). After a scope change, reconnect for it to take effect.

Scopes​

Select scopes individually during authorization. A client can only use tools within the scopes granted.

CategoryScopes
Workspaceworkspace:read, members:read
Projects and activitiesprojects:read, activities:read
Taskstasks:read, tasks:write, tasks:assign
Questionnairesquestionnaires:read, questionnaires:analysis:read, questionnaires:responses:read, questionnaires:publish
Knowledge baseknowledge:read, knowledge:write
Websiteswebsites:read
Draftsdrafts:write
Notificationsnotifications:send
Skillsskills:read
Digital employeesemployees:read, employees:memory:read

The authorization page shows only the scopes currently available.

Tools​

Tools are exposed according to granted scopes. Common tools include:

ToolsRequired scope
get_connection_contextA valid authorized connection; no additional named scope. Returns only the connection's already-authorized workspaces and permissions
search, fetch, list_knowledge_sourcesknowledge:read
save_knowledge_linkknowledge:write
list_projects, get_projectprojects:read
list_activitiesactivities:read
list_taskstasks:read
create_task, assign_tasktasks:assign
update_task_statustasks:write
list_questionnaires, get_questionnairequestionnaires:read
get_questionnaire_analysis, get_questionnaire_resultsquestionnaires:analysis:read
list_websites, get_websitewebsites:read
create_website_draft, update_website_draftdrafts:write
list_skills, get_skillskills:read
list_employees, get_employee_contextemployees:read

Call tools/list for the available tools and parameter descriptions under your current authorization. Workspace policies and service configuration also apply; a granted scope does not guarantee that a tool is available.

If a tool is missing, call get_connection_context and inspect the target workspace's permissions: missing_scopes requires reconnecting with consent for the missing scopes; policy_blocked_scopes requires a workspace administrator; server_disabled_scopes requires a service configuration change. Refresh tools/list after the correction. Do not repeatedly broaden consent to work around policy or service restrictions.

Safety and approval​

  • All reads and writes are limited to the workspace and scopes the user authorized.
  • Creating a draft never publishes it. Outward-facing actions such as publishing a questionnaire, sending a notification, or publishing a post require a prepare_* step and the user's approval inside Guppycubed before they run.
  • List tools return at most 50 items per call with pagination, and each response has a size limit.
  • Member lookups return names and user IDs by default; email addresses are available only to workspace owners or admins.
  • Individual questionnaire responses (questionnaires:responses:read) may contain personal data respondents typed into their answers, but never account, IP, or device records.

Troubleshooting​

SymptomWhat to do
A tool is missing after authorizingFollow the get_connection_context permission diagnostics above, then refresh tools/list.
Network connection fails or is refusedCheck the endpoint hostname, network connectivity, and service availability.
An HTTP redirect is returnedUse the HTTPS MCP endpoint above directly and check whether a proxy rewrites or redirects the request.
Need to revoke accessRemove the client under Settings → Connections.