Light's MCP integration lets you use AI tools to query your financial data, search invoices, look up vendors, and run reports, without switching context.
Last updated Jul 22, 2026 · 3 min read
Your AI model runs on your machine. Light only receives the individual tool calls you trigger and returns the results. No conversation history or AI output is ever sent to Light.
Which method to use: If you use Claude.ai or the Claude desktop app, connect with the Light connector below, you just sign in with your Light account. If you use Claude Code, OpenCode, n8n, or another coding or terminal client, use a personal token instead (further down).
Light is available as a connector inside Claude, so there is nothing to install and no token to paste. You add Light and sign in with your Light account.
Make sure your account is enabled for MCP first (contact your account manager if it is not). You can connect from Claude.ai or the Claude desktop app.
You connect as yourself, so Claude only sees what your Light role already allows. Claude never sees your password, and you can disconnect at any time from Settings → Connectors, which revokes access.
To check it worked, ask Claude "What Light tools do you have?" It should list them. Then try a read-only one, for example "Show my open bills in Light."
Tokens are personal, each team member generates and manages their own. Tokens are never shown again after creation, so copy yours before closing the dialog.
Claude Code - MacBook) and optionally set an expiration datelmcp_Each user can have up to 20 active tokens. If you reach the limit, revoke unused ones from the MCP Tokens section before creating a new one.
Run this once, replacing the token with yours:
claude mcp add --transport http light-mcp https://api.light.inc/rest/ext/mcp --header "Authorization: Bearer lmcp_your_token_here"
That's it. Restart Claude Code and Light tools will appear in the tool list.
Set the token as an environment variable. Add this line to your shell profile (~/.zshrc, ~/.bashrc, etc.) and reload your shell:
export LIGHT_MCP_TOKEN="lmcp_paste_your_token_here"
source ~/.zshrc # or ~/.bashrc
Then edit ~/.config/opencode/opencode.json and add the light entry under mcp:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"light": {
"type": "remote",
"url": "https://api.light.inc/rest/ext/mcp",
"headers": {
"Authorization": "Bearer {env:LIGHT_MCP_TOKEN}"
}
}
}
}
If OpenCode shows ⚠ needs authentication, the environment variable was not in scope when it launched, open a new terminal and try again.
Step-by-step walkthrough: Connect Light's MCP server from Claude Desktop
Step-by-step walkthrough: Connect Light's MCP server from n8n
Open your AI agent and ask it something like:
"What Light tools do you have available?"
If the connection is working, it will list the Light tools it can use. You're all set.
All token management is available in Settings → Profile → MCP Tokens.
lmcp_xxxx...a3Bf)| Symptom | Likely cause | Fix |
|---|---|---|
| MCP Tokens section not visible in Settings | Feature not yet enabled for your account | Contact your account manager |
401 Unauthorized | Token revoked, expired, or not set correctly | Check Settings → MCP Tokens for the token's status; create a new token if needed |
| Tools list is empty or shorter than expected | Your Light role doesn't have access to those tools | Tools respect your existing permissions in Light, check your role in Settings → Users |
OpenCode shows ⚠ needs authentication | Environment variable was not set when OpenCode launched | Open a new terminal (with the variable exported) and try again |
{"error":{"code":-32601}} | Client version mismatch | Update your AI client to the latest version |
| Other errors | Network issues, temporary server issues, etc. | Check your network connection and try again; if the issue persists, contact support with details of the error |
Was this article helpful?

