Note: API users and key pairs need the Administrator role. Connecting Claude needs a user with the Administrator, Manager, Builder, Editor or Read Only role.
There are two ways to work with your Strategy Overview data outside the app. The Claude connector, which uses the Model Context Protocol (MCP), lets you ask Claude about your clients in plain language and make targeted changes in conversation. The API gives your own scripts and integrations REST access, through an API user and its key pair. Both see exactly what their user sees in the app: the same role, the same companies and the same templates.
Connect Claude to Strategy Overview
Each person connects with their own Strategy Overview login, so Claude sees and changes only what they can, and every change is recorded under their name. It needs a Claude plan that allows custom connectors. On Claude Team and Enterprise plans, an organization Owner adds the connector once, and everyone else clicks Connect.
To connect in the Claude web or desktop app:
In Claude, open Settings > Connectors and choose Add custom connector.
Name it Strategy Overview, and enter the URL for your account's datacenter:
North America: https://api.us.strategyoverview.com/ai/mcp
Leave Client ID and Client secret empty, then save.
Click Connect, sign in to Strategy Overview the way you normally do, and approve the request.
Important: If Claude offers a choice between individual sign-in and organization-managed authentication, pick individual sign-in. The organization option signs in with your company's Microsoft account instead of your Strategy Overview account, and the connection fails.
In Claude Code, run claude mcp add --transport http strategyoverview https://api.us.strategyoverview.com/ai/mcp (use the Europe URL for EU accounts), then run /mcp and pick Authenticate.
What Claude can do
Claude can answer questions such as "Give me a briefing on Dunder Mifflin," "Which clients are overdue for their Report this year?" or "Which admins have no MFA registered?" It reads Assessments and the Health Score, Technology, Initiatives, Plans, Goals, the Schedule and Microsoft 365 users.
When you ask, Claude can also make these changes:
Grade an Assessment item on a client's Open Report, with its status, risk, solution and budgets.
Create an Initiative, or a Plan item, from an Assessment finding.
Update an Initiative, or an item in a client's Plan: status, timing, budgets, assignee and the other fields you name.
Create or update a Goal.
Link a Goal to Initiatives and Plans, or link an Initiative to Goals, devices and Assessment items, and remove those links.
Claude never deletes anything, and every change follows the same permissions as that user has in the app. Use client, Goal and Initiative names as they appear in Strategy Overview. If a name matches more than one record, Claude asks which one you meant.
Give an integration API access
The API is for your own scripts and integrations, such as syncing data with another system. Each integration gets an API user, an account that exists only to hold its keys and can't sign in to the app. The API user's role, groups, companies and templates decide what the integration can see and change.
To set one up, an Administrator:
Goes to Settings > System > API Users and clicks Add API user.
Enters a Description, picks the Role, and sets Groups, Companies and Templates the same way as for any user, then saves.
Opens Manage API keys on that API user and, under API key pairs, clicks Generate key pair.
Enters a Name and the Private key lifetime (days), then clicks Generate.
Copies the Public key, Private key, Token URL and Scope into the integration.
Important: The private key is shown once and can't be retrieved again. If it's lost, use Regenerate private key, and the old private key stops working.
The integration sends the public and private key to the token URL for an access token, then calls the API with it. The developer documentation covers every endpoint, with examples:
North America: https://api.us.strategyoverview.com/docs
Good to know
The connector uses a person's own sign-in. API users can't be used for it, and API keys are only for the API.
Client users (External Client - Editor, External Client - Read Only) and Billing users can't use the connector or the API.
The Microsoft 365 questions need the M365 module on your account.
An account can have 3 active API users, and each API user can have 3 key pairs in use. Deactivating or deleting an API user frees its place.
A private key lasts 365 days by default; you can set 1 to 730 days. Regenerate it before the date in the Expires column.
Older API keys that were sent in a header still work, but new ones can't be made. Use a key pair for anything new.
Each connection or key can make 120 requests a minute.
When we add new things Claude can do, disconnect and reconnect the connector to see them.
Common questions
Why does Claude say it isn't authorized?
Claude says it isn't authorized when the sign-in has expired, or when the user can't use the connector: it's deactivated, in an External Client or Billing role, or an API user. Reconnect from Settings > Connectors in Claude, and check the user in Settings > System > Users.
Why does the sign-in fail or loop?
A sign-in that fails or loops usually means your account is on the other datacenter. Remove the connector and add it again with the other URL.
How do I turn off Claude's access?
Remove the connector in Claude. To stop someone's access completely, an Administrator deactivates their user in Settings > System > Users, and access stops right away.
Why can't Claude see a client?
Claude can't see a client when the signed-in user can't see it in the app. Check that user's role, groups and companies in Settings > System > Users.
Next: Arya AI Assessment Assistant