MCP
Connect an MCP client to scoped Eigenn finance tools over a remote, OAuth-discoverable endpoint.
Eigenn exposes a remote Model Context Protocol endpoint for approved finance retrieval and selected writes:
The endpoint uses streamable HTTP. OAuth-capable clients can discover Eigenn's authorization and token endpoints automatically.
Connect a Client
VS Code supports a native HTTP server entry:
{
"servers": {
"eigenn": {
"type": "http",
"url": "https://api.eigenn.io/v1/mcp"
}
}
}Claude Desktop and Cursor can bridge a remote HTTP server through mcp-remote:
{
"mcpServers": {
"eigenn": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.eigenn.io/v1/mcp"
]
}
}
}The equivalent command is:
npx -y mcp-remote https://api.eigenn.io/v1/mcpFollow the client's OAuth prompt and choose the correct Eigenn team. A programmatic MCP client can also use the same Authorization bearer header as the REST API.
Scope Controls
The MCP endpoint accepts a connection only when the credential includes at least one MCP-compatible scope. Tool registration is then narrowed by the scopes actually granted.
Examples include:
- search.read
- customers.read and customers.write
- invoices.read and invoices.write
- transactions.read
- reports.read
- bank-accounts.read
- documents.read
- tracker-entries.read and tracker-entries.write
- teams.read
A 403 response means the credential authenticated but does not include a compatible scope. A 401 can mean the credential or team context is missing.
Use a read-only key or OAuth grant for analysis workflows. Add a write scope only when the client must perform that specific write.
Tools, Resources, and Prompts
Depending on scopes, Eigenn can expose tools for:
- searching finance records
- customers
- invoices, products, templates, and recurring invoices
- transactions and categories
- bank accounts
- documents and inbox items
- reports
- tags
- team context
- tracker projects, entries, and timers
Static or team-scoped resources can include transaction categories, tags, and team information. Built-in prompts cover financial health checks, invoice follow-up, expense analysis, and customer insights.
Use the client's tool inspector to see the current list. The discovery tools can also help a client find less common read operations without assuming every internal product action is available.
Approval Boundary
MCP scopes are the server-side access control. The endpoint does not add a universal human-approval step around every tool call.
For sensitive work:
- grant read scopes first
- enable the client's own confirmation controls
- require a person to review proposed customer, invoice, cash, or ledger changes
- grant a write scope only for the bounded action
- review the resulting Eigenn record after execution
Do not describe an MCP client as read-only when its credential includes customer, invoice, or tracker write scopes.
Product Workflow Boundary
The MCP server does not expose public CRUD operations for Eigenn's workflow builder or workflow execution history. Use the Workflows product area to build and monitor product workflows.
MCP can still support a bounded AI-assisted process, such as preparing an invoice follow-up summary or investigating unusual transactions, using the records allowed by its scopes.
Troubleshooting
The client cannot discover authentication
Confirm that the server URL is exactly https://api.eigenn.io/v1/mcp and that the client supports remote streamable HTTP or mcp-remote.
The connection returns 401
Authenticate again and confirm that the OAuth grant or API key is bound to an accessible team.
The connection returns 403
Create or update a restricted credential with at least one compatible scope. Add only the resource scopes the workflow needs.
A tool is missing
Compare the requested operation with the granted scopes. Tools whose resources are outside the grant are not registered for that connection.
A product workflow operation is missing
This is expected. Workflow builder and execution operations are not documented as public MCP tools.