Light
by Light
Query your company's bills, cards, expenses and ledger data from an AI assistant. 42 listed tools, 13 of which write — including card freezes and expense submissions. OAuth sign-in, role-scoped.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Light via MCP
https://api.light.inc/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Light Tools & Capabilities (42)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Your Light role governs everything. Light names role permissions as the cause when the tool list is empty or shorter than expected. There is no scope-level narrowing available, so the role is the only control surface.
- An admin gate comes first. Accounts not enabled for MCP see no MCP Tokens section and cannot connect by either route.
- 20 active tokens per user, and a token is shown only once at creation. Light documents revocation under Settings → Profile → MCP Tokens.
- The listing is incomplete. Report editing, journal entries, reconciliation and purchase requests are advertised by Light and by Anthropic's own description, and appear nowhere among the 42 names. How many tools exist beyond the listing is not stated by any source we could reach.
- No safety annotations were read. The endpoint requires OAuth, so no
readOnlyHintordestructiveHintvalues, and no parameter schemas, are published here. The read/write split above is derived from tool names and vendor prose, not from server annotations — treat it as a reasoned classification, not a vendor assertion. - Two writes leave your ledger.
create_support_ticketreaches Light's support team andgoogle_searchreaches the open web. Neither can be recalled from the assistant. - Approval is authority, not information.
approve_taskexercises a control step that Light's audit trail attributes to you. - This page describes the hosted remote connector only. Light also ships Slack, Teams and Google Sheets surfaces and a separate in-app Light Command Interface, which Light says can reverse payments and create customer credits. Those capabilities belong to LCI, not to the MCP listing, and must not be read across.
Frequently asked questions
Can the Light MCP server move money or pay a bill?
No tool in the published listing pays anything. The 42 names Anthropic's directory carries include no pay, post, transfer or payment verb, and Light's own help article steers first-time users to a read-only check. The connector reaches payables data — searching bills and vendors — rather than the payment rails that settle them.
Why does Claude show fewer Light tools than the 42 that are listed?
Your Light role does not grant access to all of them. Light's help article lists a short tool list as a known symptom and names role permissions as the cause, pointing admins at Settings then Users. The connector inherits whatever the signed-in Light account can already reach, so two colleagues can see different tool counts on the same server.
Does the Light MCP connector send my Claude conversation to Light?
No. Light states that your AI model runs on your machine, that Light receives only the individual tool calls you trigger, and that no conversation history or AI output is ever sent to Light. Tool results flow back to the assistant. The boundary is per-call, so Light sees the queries you make but not the reasoning around them.
Do I need my admin to switch on the Light MCP server first?
Yes. Light's help article says the account must be enabled for MCP and tells users to contact their account manager if the MCP Tokens section is missing from their profile. This gate applies to the built-in Claude connector too, not only to token-based clients. It is the first troubleshooting row in Light's own table.
Which Light tools can change data rather than just read it?
Thirteen of the 42 write. They approve tasks, attach receipts and files, create support tickets, modify draft card transactions, submit expenses for reimbursement, freeze or unfreeze a card, trigger a CRM sync, and create or delete stored skills. The remaining 29 search, read or look up. Only the two delete tools remove anything permanently.
What OAuth scopes does the Light MCP server ask for?
None specific to the connector. Light's RFC 9728 resource descriptor publishes an empty scopes_supported array, and its Auth0 authorization server advertises only OIDC identity claims such as openid, profile and email. There is no application scope to grant or decline, so the consent screen carries no read-only option — access falls back to your Light role.
Can I use the Light MCP server outside Claude?
Yes. Light documents a second route for clients without a built-in connector: generate a personal MCP token in Settings then Profile, and point the client at the token endpoint. Light shows worked configurations for Claude Code and OpenCode. Tokens are personal, capped at 20 active per user, and shown only once at creation.
Sources
- Light help centre, "Connect your AI assistant to Light" (retrieved 2026-08-21). Server-rendered; the article body is delivered in the page's React payload rather than in static
<main>markup, so a plain tag-stripping fetch reads as near-empty. It is not a soft 404. · retrieved 2026-08-21 - Light, "The Light MCP" product page (retrieved 2026-08-21) · retrieved 2026-08-21
- Light machine-readable index — and (retrieved 2026-08-21) · retrieved 2026-08-21
- Light, "Flash #10: Custom Agents, Claude connector, audit trails" (retrieved 2026-08-21) · retrieved 2026-08-21
- Live OAuth posture check: anonymous
initializeon both endpoints returned 401 with aWWW-Authenticatechallenge; RFC 9728 resource metadata resolved at four probe paths (2026-08-21) · retrieved 2026-08-21 - Auth0 authorization server metadata (retrieved 2026-08-21) · retrieved 2026-08-21
- Anthropic Connectors Directory entry (snapshot 2026-08-16) · retrieved 2026-08-16
- Light support — <mailto:support@light.inc> · Privacy
- Light's
robots.txtpublishesContent-Signal: search=yes, ai-input=yes, ai-train=yes, expressly permitting AI synthesis of its content.
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Light
- Tools
- 42
- Domain
- api.light.inc
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.