Documentation navigation
Government Context MCP
Authentication
How Government Context identifies users and organizations without API keys.
Browser-based OAuth 2.1
Government Context is an authenticated OAuth resource server. When a client connects to https://mcp.governmentcontext.com, it discovers the authorization service, opens a browser sign-in, and receives a token scoped to this MCP resource.
You never copy an API key or expose your password to the AI client. WorkOS handles credentials; Government Context validates the token on every request.
Identity and organization
Every request resolves to a Government Context user and the selected organization carried by the authenticated session. Tools never accept an organization ID chosen by the model.
Create your free Government Context account on the website before connecting. A valid WorkOS identity that is not linked to a Government Context account receives an explicit account-link-required response with the signup URL; it is not treated as an invalid token.
The selected organization determines free or paid data access and the rate limit. Downgrading does not invalidate a connection; subsequent calls receive the supported free-tier view.
What tools may change
Read tools inspect public government records. Follow and unfollow are the only planned write operations in the initial surface, and clients should show their normal tool-approval UI before invoking them.
