Skip to content
Baselumen is in private alphaSee the CRM

Your agents, in the CRM.
One MCP server.

Connect any MCP client once, by signing in with your Stacklumen account or with a token scoped to exactly what it may do, and your agent works in Baselumen the way you do: the CRM’s deals, contacts, clients and projects through the same routes as its screens, and 21 tools besides, audits included.

Server address

https://www.baselumen.com/app/api/mcp

Client settings

{
  "mcpServers": {
    "baselumen": {
      "url": "https://www.baselumen.com/app/api/mcp"
    }
  }
}

Discovery answers at https://www.baselumen.com/.well-known/oauth-protected-resource.

Connect once. Two ways in.

Add the server to any MCP client, then sign in or hand it a token.

  1. Sign in

    The server answers OAuth discovery, so a client that supports sign-in sends you to your Stacklumen account and back. Nothing to paste, and you choose what it may do.

  2. A token

    Mint a bl_ token in Agents and API keys, for the whole workspace or one client, with only the scopes it needs.

  3. Any client

    Claude, an editor, or your own agent: anything that speaks MCP over HTTP connects the same way.

Scoped to the task. Nothing more.

Every tool spends one scope, and a credential only sees the tools its scopes reach. A token can also be narrowed to a single client.

audits:read
List the audits and read the workspace’s saved reports
audits:run
Run audits against public URLs, spending the workspace’s monthly tool runs
signatures:read
Read the team’s email signatures, designs and install links
signatures:write
Make and change signature designs and people’s signatures, and email people their install links
clients:read
Read the client list
account:read
Read your profile, settings, the workspace and its members
account:write
Update your profile, settings and the workspace details

21 tools. Audits included.

An agent can run an audit as your workspace, read the report, and compare it with the last run on the same site, and make and send the team's email signatures.

The design library is Stacklumen's: its tools are on Stacklumen's MCP server, https://www.stacklumen.com/terminal/api/mcp, with the same sign-in.

Audits 4 tools

list_audits
The audits an agent can run with run_audit: each one’s slug, name and what it checks. audits:read
run_audit
Run one audit against a public URL, as this workspace. audits:run
list_reports
The workspace’s saved audit runs, newest first: id, tool, target, status, score and when. audits:read
get_report
One saved run: its score, the failing checks worst first, the previous successful run of the same audit on the same host to compare with, and the report’s address in the app. audits:read

Your workspace 8 tools

whoami
The workspace this token belongs to, the token name, its scopes, and its reach (whole workspace or one client). Any credential
get_profile
Your profile in the suite — name, handle, headline, bio, job title, location, links, skills and whether it is public. account:read
update_profile
Update your profile. account:write
get_settings
Your settings — theme, density and which emails you receive. account:read
update_settings
Update your settings. account:write
get_workspace
The workspace — name, kind, industry, size, description — and its members with their roles. account:read
list_members
The workspace's members and pending invitations, with roles. account:read
update_workspace
Update the workspace's details. account:write

Clients 1 tool

list_clients
The workspace's clients — id, name, slug, website, status, industry. clients:read

Signatures 7 tools

list_signature_designs
The workspace’s email signature designs: id, name, layout, colour, type, which details show, its links (each with its icon), the photo’s shape, the icons’ style, the verified badge, the button, the brand ribbon (and its animation), the extra pictures, the Made with Baselumen card, whether it carries a banner, its version, and how many people wear it. signatures:read
get_signature
One person’s signature as it is now: their details, the design they wear, where it is (draft, sent, installed, or out of date), the signature’s HTML and plain text, and their install link (a page that copies it and shows the steps for their mail app). signatures:read
create_signature_design
Make a signature design. signatures:write
update_signature_design
Change a design. signatures:write
generate_team_signatures
Give people signatures in a design: the workspace’s members (filled from their profiles: name, address, job title, pronouns), a list of people, or both. signatures:write
update_person_signature
Change one person’s signature: their details, the design they wear (design_id, or null for the first), or which details show for them alone (overrides). signatures:write
send_signature_installs
Email people their signature with its install link: person_ids, all: true, or stale: true (everyone whose installed copy is behind). signatures:write

More 1 tool

list_audit_events
The workspace's audit log, newest first: who did what and when (invitations, removals and role changes, deleted Library files, room links revoked, deals, contacts and companies deleted, merged, imported and exported, apps and services connected, tokens made, exports), each with its target and where it came from. account:read

Give your agent the tools. Keep the keys.

Sign in from any MCP client, or mint a token scoped to one client and only the work it should do.