Skip to content

Connect an AI assistant (MCP)

Linyup runs a remote MCP (Model Context Protocol) server, so you can connect an AI assistant to your studio and ask questions in plain language:

  • “Who hasn’t come in three weeks?”
  • “How full were Thursday classes last month?”
  • “What did we earn from drop-ins in August?”

Access is limited to what you allow, area by area. Everything is read-only except events: set Events to Read & edit and the assistant can also create events and change their title, dates, place and description (create_event, update_event). New events start private, and nothing can be deleted or cancelled through a connection. Editing also needs a role that manages events where it acts. One connection can reach every studio and organization you work in: you choose which when you connect.

Tool What it answers
get_studio_overview A summary of your studio
find_contacts, get_contact, get_contact_history Finding people and their history
list_inactive_contacts Who has stopped coming
get_schedule, get_session_roster, list_events What’s on, and who’s booked
list_offerings, list_memberships What you offer and who holds which plan
get_attendance_trend, get_class_fill_rates Attendance and fill rates over time
get_revenue_summary Revenue

In an organization, the assistant can look up the organization itself (get_organization_overview), its member studios (list_member_studios) and its own events (list_events). A studio’s people, classes and money stay with that studio: connect the studio too if you work there.

When a connection reaches more than one place, every tool takes a workspace and list_workspaces shows the choices. If you don’t say which studio or organization you mean, the assistant asks.

The server address is https://api.linyup.com/mcp. A studio needs the API & AI connectors add-on; an organization has it with the Organization plan.

claude.ai, ChatGPT, VS Code and other assistants with remote connectors: add a custom connector with that address. The assistant sends you to Linyup to sign in. There you turn on the studios and organizations it may reach, check what it may read, and approve. You see and disconnect your connections under Your account → Connected apps. A studio owner sees every connection that reaches the studio under Settings → API keys, and can remove a connection’s access to the studio there. An organization admin finds the same, and the organization’s own API keys, under API keys in the organization’s settings.

Claude Code and other tools that take a header: create an API key under Settings → API keys (the screen shows this command with your key filled in), then run:

Terminal window
claude mcp add --transport http linyup https://api.linyup.com/mcp \
--header "Authorization: Bearer lyp_live_…"

The assistant sees only what the key’s scopes allow, and only what you yourself may see in the app.