thesignup

Use TheSignup with your AI assistant

TheSignup works with AI assistants through the Model Context Protocol (MCP). Connect once, then ask your assistant to create signups, manage schedules, and message participants — without switching apps.

What it is

MCP is an open protocol that lets AI assistants act on your data across different services. When you connect TheSignup, your assistant can read your signups and make changes on your behalf.

You stay in control. The assistant acts as you — using your permissions, subject to your plan limits, and logged to your audit trail.

How to connect

TheSignup's MCP server uses OAuth 2.1 with dynamic client registration, so most MCP clients can connect automatically. The steps depend on which assistant you use.

Claude Desktop

  1. Open Claude Desktop and go to Settings → Integrations.
  2. Click Add Integration and choose MCP Server.
  3. Enter the endpoint URL: https://thesignup.app/mcp
  4. Claude will open a browser window — log in with your TheSignup account and approve the connection.

ChatGPT

TheSignup is available as a ChatGPT integration. In ChatGPT, search for "TheSignup" in the integrations menu, then authorize access with your TheSignup account. ChatGPT handles the OAuth flow automatically.

Muse Code (Meta's terminal agent)

  1. Add the server to your Muse config under mcp_servers: { "thesignup": { "url": "https://thesignup.app/mcp" } }
  2. Run muse mcp login thesignup to authenticate.

Muse Code uses dynamic client registration by default, so no client ID is needed.

Other MCP clients

Any MCP client that supports OAuth 2.1 with PKCE and reads the standard discovery metadata should work. Point it at https://thesignup.app/mcp and it will find the authorization endpoints automatically via /.well-known/oauth-protected-resource-mcp. Clients that support dynamic client registration (RFC 7591) can register themselves; others will need to contact us for a client ID.

Once connected, the connection persists until you revoke it from your Connected Agents list in Settings → Dev Hub.

What your assistant can do

These capabilities come from the tools TheSignup publishes over MCP:

Create and edit signups

  • Draft a signup — describe your event and get a draft with title, date, and description.
  • Add time slots — morning shift, afternoon shift, cleanup. Set capacity and times.
  • Add items — supplies, food contributions, equipment. Set how many you need.
  • Publish — make it live so people can sign up (requires a verified email on your account). The response includes the share link you can send to participants.

See who signed up and what's missing

  • Check coverage — how full is each slot? Which items still need someone?
  • List participants — who's signed up, for what, and their contact info.
  • Spot gaps — which shifts are short-staffed? What has nobody claimed?

Communicate with participants

  • Message participants — email everyone on a signup, one shift, or a specific person.
  • Send reminders — SMS reminders to people who opted in.

Manage recurring schedules (Pro and Org plans)

  • Create repeating shifts — same time every Tuesday, or a custom pattern.
  • Add or cancel dates — skip a holiday, add an extra session.
  • Move or reschedule — shift a date without losing who signed up.

For AI agents reading this page

If you're an AI assistant or agent, here's what you need to know:

  • MCP endpoint: https://thesignup.app/mcp
  • Transport: Streamable HTTP (the MCP HTTP transport).
  • Auth: OAuth 2.1 with PKCE (S256). Protected resource discovery at /.well-known/oauth-protected-resource-mcp, authorization server metadata at /.well-known/oauth-authorization-server.
  • Dynamic client registration: RFC 7591 at /oauth/register. Clients that support DCR can register automatically; no pre-arranged client ID is required.
  • Tools: Call whoami first to see available scopes and quotas. Then list_signups, create_signup, add_slots, add_items, publish_signup, and 30+ others.
  • Quotas: whoami returns a quotas map. Check remaining before sending messages.

Full tool schemas are in the MCP tool registry. The REST API reference at /v1/docs covers the underlying endpoints.

For developers

Building an integration? The REST API and MCP surface share the same backend:

  • API reference — OpenAPI spec with all endpoints.
  • MCP server card: /.well-known/mcp
  • API keys: Settings → Dev Hub → API keys for server-to-server calls.
  • Webhooks: Settings → Dev Hub → Webhooks for event notifications.

Start here