Bonsai MCP

Live

OAUTH 2.0

PRODUCTIVITY

Productivity

Connect to Bonsai, the all-in-one business management platform for freelancers and agencies. Manage projects, tasks, CRM contacts, deals, invoices, and...

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Bonsai MCP
agent · Acme Q3
Run
Create Company in Bonsai MCP
S
bonsaimcp_create_company
85ms
Bonsai MCP agent
Create a crm company in the user's bonsai account. requires name. optionally set a default contact and domains. search w.
Sources: Bonsai MCP
bonsaimcpmcp
1 tool call
18:29
Message Claude...

Bonsai MCP tools for AI agents

CALL ANY TOOL
12 tools covering create.
bonsaimcp_create_company
Create company
Create a CRM company in the user's Bonsai account. Requires name. Optionally set a default contact and domains. Search with list_companies first to avoid duplicates.
Parameters
Name
Type
Required
Description
name
string
Required
The name of the company to create.
default_contact_id
integer
Optional
Optional ID of the default contact for this company.
domains
array
Optional
Optional list of email domains associated with this company.
bonsaimcp_create_contact
Create contact
bonsaimcp_create_invoice
Create invoice
bonsaimcp_create_invoice_item
Create invoice item
bonsaimcp_create_project
Create project
bonsaimcp_create_task
Create task
bonsaimcp_create_time_entry
Create time entry
bonsaimcp_get_task
Get task
bonsaimcp_list_board_groups
List board groups
bonsaimcp_list_companies
List companies
bonsaimcp_list_contacts
List contacts
bonsaimcp_list_deals
List deals
bonsaimcp_list_invoices
List invoices
bonsaimcp_list_projects
List projects
bonsaimcp_list_tasks
List tasks
bonsaimcp_list_team_members
List team members
bonsaimcp_update_company
Update company
bonsaimcp_update_contact
Update contact
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="bonsaimcp")

mcp = MultiServerMCPClient({
"bonsaimcp": {
"url": "https://mcp.scalekit.com/bonsaimcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "bonsaimcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/bonsaimcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "bonsaimcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/bonsaimcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="bonsaimcp")
# Connect to MCP at https://mcp.scalekit.com/bonsaimcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Create a CRM company in the user’s Bonsai account?
Copy the prompt
Copied
Fetch a single task from Bonsai by its UUID?
Advanced
Copy the prompt
Copied
List board groups (pipeline stages for deals, project groups for projects) in the user’s Bonsai company?
Copy the prompt
Copied
Update an existing CRM company in Bonsai?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Bonsai MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Bonsai MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Bonsai MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Bonsai MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
People Ops and HR teams
Performance review collector
Collects review feedback from Airtable and Google Forms scoped to each manager's direct reports, writes per-employee summaries to Notion, and DMs the manager a Slack digest.
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
PEOPLE OPS
Performance review collector agent
Collect review feedback from Airtable and Google Forms per manager, summarise each report in Notion, and DM the digest in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Bonsai as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Bonsai OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Bonsai?
Yes. Pass a tool name filter to listScopedTools so the productivity agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Bonsai.

What happens when a user revokes Bonsai access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent create invoices on behalf of anyone?
Only the authorizing user. Invoices, projects, and CRM writes run under that freelancer or agency seat in Bonsai, so billing actions always attribute to the right person.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""bonsaimcp"": {
""url"": ""https://mcp.scalekit.com/bonsaimcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.bonsaimcp]
url = ""https://mcp.scalekit.com/bonsaimcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""bonsaimcp"": {
""url"": ""https://mcp.scalekit.com/bonsaimcp"",
""type"": ""http""
}
}
}