Claude Instrumentl connectorWhat Claude can do in your Instrumentl account.
The Claude Instrumentl connector exposes 6 tools. 4 of them read your grant data, 0 write anything, and 2 are documented nowhere. Below: what Claude can look up, the approval setting Instrumentl turns on by default, and the gaps in what it sees.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can read Instrumentl
Grant prospecting means clicking through projects, match lists and a tracker to answer one question: what should we apply for next? With the connector, a development officer asks Claude directly, and it pulls the projects, recommended matches and saved grants from the Instrumentl account so the answer comes with the real list behind it.
Matches for one program, filtered. Ask for the recommended grants for your literacy project: Claude finds the project with list_projects, then calls list_project_matches to bring back its matches.
A view of what the team already keeps. list_grants shows the grants your team has saved, hidden or added by hand, useful before a board meeting.
A sanity check on the connection. get_current_account tells you which Instrumentl account Claude is signed into, handy for consultants who switch between clients.
What it does not do on this sheet: the directory lists no writing tool. Instrumentl's own documentation describes saving matches, updating tracked grants and logging expenses, but those tools are absent from the public sheet we read, so this page does not count them. Claude also cannot see the cycle or fiscal year you chose for a saved grant. And nothing runs by itself: no deadline reminder fires unless you ask. Hands-off flows belong to automation tools, a different job; the Integrations hub covers that.
Five words before you connect
The Claude vocabulary this page relies on, in under a minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector hands to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use afterwards. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for in the chat before it goes ahead with something that would change your account.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Instrumentl.
Connect Instrumentl to Claude in three steps
- 01
Find Instrumentl in Claude
Open Claude's settings, go to Customize then Connectors, and look up Instrumentl in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Instrumentl in the window the service opens itself. If the link breaks later, use Disconnect and connect again from the same row.
- 03
Read the authorization screen
Check the screen Instrumentl shows before you accept it. It belongs to the service, not to Claude, and it is what sets what the access covers. Access granted there can also be withdrawn later from the Instrumentl side.
The 6 tools, split by what is known
Instrumentl gives Claude 6 tools: 4 that read your account, 0 that change something in it, and 2 no official source describes.
Four tools read, two are listed with no description. Tool names stay exactly as Claude shows them.
- 4 read
- 2 not documented
What Claude reads (4)
4 toolsFour tools that look at your Instrumentl data and leave it unchanged.
get_current_account
Tells you which Instrumentl account Claude is connected to right now. A quick way to confirm you are looking at the right organization's data.
list_grants
Returns the grants your team has saved, hidden or entered itself in Instrumentl, so Claude can sort or summarize them for you.
list_project_matches
Brings back the recommended grant matches for one of your projects. Claude can then filter them, for example by deadline, inside the conversation.
list_projects
Lists every project set up in your Instrumentl account. Each project it returns is the entry point list_project_matches needs to bring back recommended grants.
Undocumented (2)
2 toolsThe directory publishes these two names and nothing more. No official text says what they do, so this page does not guess.
get_grant
This name appears in the directory's tool list, and that is all any official source offers. Instrumentl's guides do not mention it, so its effect stays unknown here.
get_match
No official source documents this one. It is listed on the directory sheet, yet neither of Instrumentl's two help articles names it, and no Claude page covers it. Its behavior is therefore not described here at all.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account in your name. Instrumentl goes further: it says every one of its tools starts out set to require approval on every request.
You can loosen that per tool, or by type, for instance always allowing read-only tools while write and delete tools keep asking. On Team and Enterprise workspaces, owners decide whether members may let actions through without a prompt, and they can restrict what a connector does across the organization; nobody overrides that from a personal account. Claude works with the rights of the person who connected, and Instrumentl adds that its workspace access controls and user permissions apply as usual.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer, connector by connector, is published nowhere.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state, the Instrumentl sheet in the official directory is the place to look.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a new match appears or a deadline nears.
Everything here comes from the directory sheet and Instrumentl's help articles: no Claude help page covers this connector. By default the sheet exposes reading only, and that list is an observed floor, not a promise; Instrumentl's documentation already describes writing tools the public sheet does not show. The partner badge is not a security audit, and Anthropic says on every sheet it neither picks a publisher's tools nor guarantees their behavior.
Need help connecting Instrumentl to Claude?
A person reads every message.
