Skip to main content
The Campground MCP (Model Context Protocol) server lets external AI assistants — such as Claude.ai’s connectors — read data from your organization on your behalf. Connections are authorized through OAuth 2.1, so the assistant never sees your password and you can revoke access at any time. Each organization has its own MCP endpoint scoped to its subdomain, so signing in to Claude with your-org.campground.fyi connects the assistant to that organization specifically. Consent always happens on your organization’s subdomain, where your existing session and branding apply.
The MCP server is available to organizations with AI platform access enabled. If you do not see the option to connect an AI assistant, contact your Campground account manager to request access.

​
How it works

When you connect an MCP-compatible AI client to Campground:
  1. The client fetches OAuth discovery metadata from your organization’s subdomain at https://your-org.campground.fyi/.well-known/oauth-protected-resource.
  2. The metadata points the client at your organization’s authorization endpoint at https://your-org.campground.fyi/oauth/authorize.
  3. You are sent to the consent page on your organization’s subdomain, where you sign in (if you are not already) and approve the requested access.
  4. After you approve, the assistant receives an access token it can use to call the MCP server.
Because the entire OAuth handshake stays on your tenant subdomain, the AI client connects to the correct organization without any extra configuration on your part.

​
Connect Claude to your organization

Prerequisites:
  • An active Campground account with access to your organization’s platform.
  • AI platform access enabled for your organization (ask your admin if you are unsure).
  • An AI client that supports the Model Context Protocol, such as Claude.ai.
To connect Claude:
  1. In Claude, open Settings > Connectors and select Add connector.
  2. Enter your Campground organization URL — for example, https://your-org.campground.fyi — as the MCP server URL.
  3. Claude redirects you to your organization’s sign-in page. Sign in with your Campground credentials if prompted.
  4. Review the requested access on the consent screen and select Allow to authorize the connection.
  5. Claude returns to its own interface and confirms the connector is active.
You can now ask Claude questions that draw on your Campground data — for example, summarizing recent applications or pulling a list of program members — within the limits of what your account is allowed to see. The consent screen names the three parties involved in the connection so you can confirm you are authorizing the right app for the right organization:
  • The requesting app — the name and homepage of the client asking for access (for example, Claude Desktop).
  • Your organization — the Campground organization whose data will be shared, shown with its name and subdomain (for example, your-org.campground.fyi). Use the subdomain as your verification anchor: it should match the organization you intended to connect.
  • Your account — the account that is granting access.
The screen also lists exactly what the connected app can do. The hosted MCP endpoint runs in read-only mode, so connections through Claude or another MCP client can:
  • Read data in your organization, including people, programs, applications, and tasks.
  • Run queries, reports, and analytics on that data.
The hosted MCP endpoint cannot create, change, or delete anything in your organization. If you do not recognize the requesting app, or the organization subdomain does not match what you expected, select Deny and start over from the app you trust.

​
Discovery endpoints

If you are building or configuring a custom MCP client, point it at your organization’s subdomain. The following endpoints are published per tenant: Example discovery request:
The response includes an authorization_servers entry pointing at the same subdomain, so issuer-equality checks performed by strict OAuth clients succeed without additional configuration. If your organization does not have AI platform access enabled, these endpoints return 404 Not Found.

​
Revoke access

To disconnect an AI assistant, remove the connector from the assistant’s own settings. The next request the assistant makes with the revoked token is rejected, and you can re-authorize at any time by repeating the connection flow. If you suspect a token has been misused, contact your Campground admin so they can audit recent activity and, if needed, disable AI platform access for your organization.