August API & MCP

August MCP

August exposes a public Model Context Protocol (MCP) server at /api/mcp on the August web app you sign in to. Point any MCP client that supports Streamable HTTP at that endpoint and authenticate with an August API key or an OAuth access token. This is the reverse of MCP Support, which covers August connecting out to other MCP servers as a client.

The endpoint

The MCP server runs over Streamable HTTP, so your client connects straight to /api/mcp on the August web app with no separate transport setup.

  1. In your MCP client, add a new remote MCP server and set its URL to /api/mcp on the August web app.

  2. Choose how the client authenticates: an August API key or an OAuth access token.

Authenticate with an API key

An August API key identifies your user account and is the simplest way to connect a client you control.

  1. In your August account settings, open the API Keys tab and create a key. Keys start with ak_ and are scoped to your user account, so an organization-level key will not work here.

  2. Configure your MCP client to send the key in the Authorization header as a bearer token: Authorization: Bearer ak_....

Authenticate with OAuth

If your client signs in through OAuth instead, it uses an OAuth access token as the bearer token in the same Authorization header. The OAuth flow requires the email scope.

OAuth discovery

Clients that support OAuth discovery can find the authorization server automatically. If a client connects without credentials, the endpoint responds with an authorization challenge that points to the protected-resource metadata at /.well-known/oauth-protected-resource/api/mcp. That document is publicly available and tells a compatible client where to start the OAuth flow, so you do not need to configure the authorization server manually.

What tools are available

The MCP server exposes August's public API surface as MCP tools, so your client can use the released public operations rather than a separately maintained tool list. The same operations are available through the REST API; see August API. Covered areas include projects, folders, documents, chats, legal research, workflows, skills, tags, search, and uploads.

Tool names follow the API procedure paths. For example, the public API operation projects.list is exposed as projects_list.

Was this helpful?
Was this helpful?