Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Teams

Fulcrum's MCP sign-in goes OAuth (alpha)

Written November 13, 2026

Fulcrum MCP now supports OAuth 2.0 sign-in in alpha: connect a compatible client, sign in with your Fulcrum account, and skip the API token.

What changed

Fulcrum is a field data collection platform, and its MCP server is the door an outside assistant uses to reach it. Fulcrum's developer reference for Fulcrum MCP describes the server this way: it "lets any MCP-compatible client (Claude, ChatGPT, Copilot, custom agents, etc.) build and manage Fulcrum apps and query live data." The connection now has a sign-in route. The same reference states that "Fulcrum MCP supports OAuth 2.0 sign-in and API tokens. Use OAuth sign-in when your client supports it."

Fulcrum's help article puts the choice in the same order for non-technical users: two ways to connect, sign in with your Fulcrum account (OAuth) or use an API token, with sign-in the recommended option when the AI tool supports it. That ordering matters for a team. An API token is a shared secret that someone generates, pastes into a config and later has to rotate. A sign-in ties the connection to a named member of the organization, and the access follows that person's role rather than the token's reach.

The whole package — the MCP server and the companion AI Toolkit of skills — is an alpha. Fulcrum labels it an early release still in progress, with no API stability guarantees yet and breaking changes expected before general availability. The sign-in flow below is the flow Fulcrum documents today, inside that alpha framing.

How the sign-in works

Fulcrum documents five steps, and none of them involves registering your client with Fulcrum in advance:

  1. Discovery. The client discovers the authorization server from the MCP endpoint, using standard MCP authorization discovery.
  2. Client identification. The client identifies itself with a Client ID Metadata Document. Its client ID is the HTTPS URL of its JSON metadata document, and no pre-registration with Fulcrum is needed. Fulcrum's example is VS Code, whose client ID is its published metadata URL.
  3. Login. You sign in with your normal Fulcrum login, including SAML single sign-on where your organization uses it.
  4. Consent. The consent page shows the requesting client's name and your organization, with Allow access and Deny access buttons.
  5. Token. Fulcrum issues short-lived access tokens and forwards them to the underlying App MCP and Query MCP services.

The consent step is where the access boundary is set. Allowing access authorizes the client for what the signed-in member is permitted to access — no more. Denying it returns an access denied response to the client and issues no token. Fulcrum's help article gives the expected outcome in plain terms: you return to your AI tool with Fulcrum MCP connected, and "your assistant can see and change only what your Fulcrum role allows."

What the connection reaches

There is one endpoint per region, and you use the endpoint that matches your organization's Fulcrum instance rather than your physical location, with no automatic fallback between regions: https://mcp.fulcrumapp.com for the United States, and matching regional endpoints for Australia, Europe and Canada. The single endpoint is unified — it exposes both tool groups over Streamable HTTP:

Do not confuse the server with the AI Toolkit sold alongside it. The Toolkit is a library of skills — prompt-level guidance that teaches a client Fulcrum's platform conventions, such as field types and safe automation patterns. It is not a server, it currently does not bundle or configure any MCP server itself, and its mcp.json is intentionally empty. The two install independently and are meant to be used together: the Toolkit carries the know-how, the MCP connection carries the ability to act.

Alpha limits

For a team lead, the practical read is narrow. If your assistant supports sign-in, connect it with OAuth and let each person's Fulcrum role draw the boundary, instead of spreading one API token across the team. Keep the token route for the tools that cannot sign in yet, and plan on the alpha changing under you — that is the deal Fulcrum states up front.

Related playbooks

Sources

Back to: Teams playbooks hub · Also: Iterable's hosted MCP server reaches your AI tools