How to use with Grok
Connect Grok to your Awaken account through the remote MCP server, either by signing in from the Grok connectors page or by giving a Grok Bot an API key.
Before you begin
Awaken API access is currently in beta and requires a Dolphin or Whale plan. If the API Keys page says access is not enabled for your client, email beta@awaken.tax to request it.
There are two ways to connect Grok. The connectors page uses OAuth: you sign in to Awaken and no key is copied anywhere. A Grok Bot can instead be given an API key in an explicit Authorization header.
Option A: add a connector and sign in
Awaken accepts Grok's published client identity (https://grok.com/oauth/mcp-client.json). If the connectors page still reports invalid_client, the server you are connecting to predates Grok support; use Option B in the meantime.
1. Add a custom connector
Open grok.com/connectors, choose to add a custom connector, and enter the server URL https://mcp.awaken.tax/mcp.
2. Sign in to Awaken
Grok opens Awaken in your browser. Sign in with the account that has access to the workspace you want to connect.
3. Choose a client and scope
The consent page shows grok.com as the requesting app. Pick the Awaken client Grok may access and allow read only or read + write, then approve. Grok receives a token scoped to that client and refreshes it automatically.
Option B: create an API key for a Grok Bot
Do not paste the key into a shared chat or commit it anywhere. If it is exposed, expired, or no longer needed, revoke it from Settings → API Keys and create a replacement.
1. Open API Keys
In the Awaken workspace you want to connect, open Settings → API Keys and select Create API Key.
2. Choose access
Give the key a recognizable name, choose Read for analysis or Read + Write only when Grok should edit data, and optionally set an expiration.
3. Copy the secret and client ID
Copy the awaken_… secret when it appears; for security, it cannot be viewed again. Also copy the client ID shown on the API Keys page. The key is scoped to that client only.
Build the Authorization header
Grok sends a single Authorization header, so combine the client ID and API key into one bearer token separated by a colon. Awaken's MCP server accepts this format in place of separate Authorization and x-client-id headers.
Authorization: Bearer YOUR_CLIENT_ID:YOUR_API_KEY
Add the server to a Grok Bot
Open or create a Grok Bot and ask it to add Awaken as a remote MCP server. Replace YOUR_CLIENT_ID and YOUR_API_KEY with the values from the API Keys page. Because the header is provided explicitly, Grok does not start an OAuth sign-in and authenticates with your API key directly.
Add a remote MCP server named "awaken" at https://mcp.awaken.tax/mcpusing the Streamable HTTP transport. Send this header on every request:Authorization: Bearer YOUR_CLIENT_ID:YOUR_API_KEY
Verify the connection
Ask the bot to list the tools available from the awaken server. If it can see tools such as listing accounts or transactions, the connection is working. If the server is reachable but requests fail with an authentication error, re-check that the bearer token is the client ID and API key joined with a colon.
Review
Show my largest taxable events this year and flag anything missing cost basis.
Clean up
Find my unreviewed transactions, explain the likely labels, and ask before changing anything.
Reports
Generate my Form 8949 report for 2025 and tell me when it is ready.
How the OAuth path works
Grok identifies itself with a client metadata document hosted at grok.com rather than registering a new client on each connection, so Awaken can allowlist it the same way it does ChatGPT and Claude.