BlackLine MCP connector
The BlackLine connector brings BlackLine users, teams, roles and reports into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can manage access and pull reports from a chat window inside their own BlackLine permissions.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
22 tools
How to connect
How to connect BlackLine to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect BlackLine once
-
Open Connections, choose Add connection, and pick BlackLine.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a BlackLine API key. One person generates a token in BlackLine and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
BlackLine MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
BlackLine MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
BlackLine MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect BlackLine to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with BlackLine through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Accounting
Bring a new accountant into BlackLine on day one
Create the user, add them to the right close team and assign the role they need before their first reconciliation lands.
-
Finance systems
Clean up roles after a reorganization
List every BlackLine user and their roles, spot people carrying permissions they no longer need, and remove or reassign roles in one pass.
-
Internal audit
Answer who has access to what
Pull the full list of BlackLine users, teams and product roles so a segregation of duties review starts from live records rather than a stale spreadsheet.
-
Controllership
Reshape close teams as entities change
Create a team for a new entity, move preparers and reviewers between teams, and retire teams that no longer map to the ledger.
-
IT
Offboard a leaver from BlackLine fast
Remove a departing employee from their BlackLine teams and roles, or delete the user entirely, the same afternoon HR confirms the exit.
-
Finance operations
Find the right BlackLine report quickly
Ask for the available BlackLine reports, open the one you need by name and read what it covers without clicking through the reporting menu.
Try asking
- “Who is on the Entity 12 close team in BlackLine?”
- “Add Priya Shah to the Treasury team as a preparer”
- “List every BlackLine user with an administrator role”
Compare
Elaichi vs Zapier MCP vs Composio for BlackLine
All three can connect BlackLine to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over BlackLine tools | Allow or restrict single BlackLine tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per BlackLine call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
BlackLine tools for your AI agents
22 tools are ready to call through Elaichi's MCP endpoint the moment you connect BlackLine, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting BlackLine gets you
6 screens from the product, each doing one job for your BlackLine account.
The agent
Ask about BlackLine users and get live answers.
Plain questions about BlackLine users, teams and roles come back from current records.
- users
- teams
- roles
- reports
Ask Elaichi to work across your apps.
Who is on the Entity 12 close team in BlackLine?
Add Priya Shah to the Treasury team as a preparer
List every BlackLine user with an administrator role
Also runs in Claude, ChatGPT or Cursor
MCP clients
Use BlackLine from any MCP client.
Claude, ChatGPT and Cursor share one governed endpoint with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
22 BlackLine tools, with no code to write.
Users, teams, roles, reports and tokens are covered without an engineer building anything.
- List all BlackLine users
- Get single BlackLine user by ID
- Create a BlackLine user
- Update a BlackLine user by ID
ElaichiToolsToolboxes
Each team gets its own BlackLine toolbox.
Accounting, IT and internal audit each see the BlackLine tools their work calls for.
- Accounting
- Finance systems
- Internal audit
- Controllership
ElaichiToolboxesShared connections
Teammates work through BlackLine without the key.
One person connects BlackLine, shares it, and nobody else ever handles the credential.
- Accounting
- Finance systems
- Internal audit
- Controllership
ElaichiConnectionsAudit log
Every BlackLine change is written down.
See who assigned which role or edited which team, and exactly when.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule does the BlackLine access review.
BlackLine users are fetched, grouped by team, summarized, approved by a person, then posted back.
BlackLine digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
BlackLine
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
BlackLine
Queued
Collections and dashboards
BlackLine access health, refreshed on a schedule.
Users created, roles held and teams covered, computed from BlackLine with no model involved.
BlackLine health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Teams
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Accounting 34%
Finance systems 27%
Internal audit 21%
Controllership 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect BlackLine to Claude?
Open Elaichi, choose BlackLine from the catalog and paste in a BlackLine API key; that is the only sign-in step, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and BlackLine is ready to use.
Does BlackLine work with ChatGPT and Cursor as well as Claude?
Yes. Once BlackLine is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect BlackLine once and every client picks it up.
What can an AI agent actually do with my BlackLine data?
With BlackLine connected, an agent can list and look up BlackLine users, teams, roles and product roles, create or update users and teams, add people to teams, assign or remove roles, and find and open BlackLine reports. In practice that means asking things like who is on the Entity 12 close team or which users hold an administrator role, and getting an answer from live BlackLine records. Short, concrete asks work better than long sentences.
Does connecting BlackLine give the AI access to every user, team and role?
No. Every call to BlackLine runs inside the permissions of the person who signed in, so an agent can only see and change the BlackLine users, teams and roles that person could already manage. Elaichi can narrow that further with restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in BlackLine?
Yes. Restrictions in Elaichi work per action, so you can allow reading BlackLine users and reports while blocking deleting users, removing roles or editing teams. A restricted action is left out of the AI client's tool list entirely, so it cannot be called no matter what someone types.
What happens to a BlackLine connection when someone leaves?
Offboarding a person in Elaichi ends their access to BlackLine through every AI client at once. If they had shared a BlackLine connection with their team, that connection keeps working for everyone else. Disconnecting BlackLine once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the BlackLine MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. BlackLine is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for BlackLine?
Yes. Both let Claude, ChatGPT or Cursor use BlackLine. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every BlackLine call.
How is Elaichi different from Composio for BlackLine?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to BlackLine: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put BlackLine in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.