Log In Sign up
Model Context Protocol

Cobot MCP Server

Connect AI assistants that speak the Model Context Protocol (MCP) to your Cobot space and manage it in plain language.

Getting started

Add the MCP server to your MCP client as a remote server using this URL: https://api.cobot.me/mcp

Setup with your AI assistant

Each client has its own steps for adding a remote MCP server. Follow the guide for yours:

  • Claude — custom connectors with remote MCP
  • ChatGPT — connect a remote MCP server (Developer mode)
  • Mistral — custom MCP connectors in Vibe

What you can do

Once connected, you can ask your assistant to, for example:

  • “Book the meeting room for Jane tomorrow from 10 to 12.”
  • “Which desks are free this afternoon?”
  • “List today's bookings.”
  • “Show me all unpaid invoices of this month.”

Available tools

  • get_current_user — the logged-in user and the spaces they administer
  • list_resources — rooms, desks and other bookable resources
  • check_resource_availability — free resources in a time range
  • list_memberships / get_membership — members of a space
  • list_teams / get_team — teams and their members
  • list_contacts / get_contact — non-member contacts
  • list_products / get_product — extras, booking add-ons and charges
  • list_invoices / get_invoice — review invoices
  • list_external_bookings / get_external_booking — visitor/non-member bookings
  • list_allocations — long-term resource allocations
  • create_booking — book a resource, optionally for a member
  • list_bookings / get_booking / update_booking — review and update bookings
  • list_membership_check_ins — a member’s check-in history
  • check_out — check a member out

Security

  • Authorization uses OAuth 2.0 with PKCE — the same mechanism as the Cobot API. No passwords or API keys are shared with the assistant.
  • Access is limited to spaces you are an admin of and the permissions granted to you in each.
  • You can revoke an assistant's access at any time under authorized applications.

For MCP client developers

The server implements the streamable HTTP transport (stateless, no SSE) and standard OAuth discovery:

  • Protected resource metadata (RFC 9728): https://api.cobot.me/.well-known/oauth-protected-resource/mcp
  • Authorization server metadata (RFC 8414): https://www.cobot.me/.well-known/oauth-authorization-server
  • Dynamic client registration (RFC 7591) for public, PKCE-only clients: POST https://www.cobot.me/oauth/register

Questions or feedback? Contact us at support@cobot.me.