Klipfolio MCP server for AI agents

Live

API KEY

DASHBOARDS

Analytics

Klipfolio gives your agent dashboard operations in each user's Klipfolio account: build dashboards and Klips, manage and refresh data sources, share with groups and users, and publish dashboards as links.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Klipfolio
agent · Acme Q3
Run
Which Klips are on the Sales Overview dashboard?
S
klipfolio_dashboard_klip_instances_list
98ms
Reporting agent
The Sales Overview dashboard has 6 Klips, including Pipeline by Stage and Monthly Bookings.
Sources: Klipfolio, 1 dashboard, 6 Klips
klipfolio
6 Klips
18:29
Message Claude...

Tools your reporting agent reaches for on Klipfolio, scoped per user.

CALL ANY TOOL
59 tools for dashboards in Klipfolio: create and lay out dashboards, build Klips, manage and refresh data sources, share with groups and users, and publish links.
klipfolio_client_get
Get client
Get one client account by ID. Returns its id, name, description, status, seats, billing and trial details; with full=true also its user and group IDs and share rights. Use klipfolio_client_get when you know the client ID. Use klipfolio_clients_list to find it.
Parameters
Name
Type
Required
Description
client_id
string
Required
ID of the client account. Get it from the id field of klipfolio_clients_list. Example: "0123456789abcdef0123456789abcdef".
full
boolean
Optional
Set to true to include associations in the response (users, groups, share_right). Default false.
klipfolio_clients_list
List clients
klipfolio_dashboard_create
Create dashboard
klipfolio_dashboard_delete
Delete dashboard
klipfolio_dashboard_klip_instance_remove
Remove dashboard klip instance
klipfolio_dashboard_klips_add
Add dashboard klips
klipfolio_dashboard_layout_get
Get dashboard layout
klipfolio_dashboard_layout_update
Update dashboard layout
klipfolio_dashboard_share_right_delete
Delete dashboard share right
klipfolio_dashboard_share_rights_update
Update dashboard share rights
klipfolio_dashboards_list
List dashboards
klipfolio_datasource_create
Create datasource
klipfolio_datasource_disable
Disable datasource
klipfolio_datasource_get
Get datasource
klipfolio_datasource_instance_refresh
Refresh datasource instance
klipfolio_datasource_properties_get
Get datasource properties
klipfolio_datasource_properties_update
Update datasource properties
klipfolio_datasource_share_right_delete
Delete datasource share right
klipfolio_datasource_update
Update datasource
klipfolio_datasources_list
List datasources
klipfolio_group_get
Get group
klipfolio_groups_list
List groups
klipfolio_klip_create
Create klip
klipfolio_klip_delete
Delete klip
klipfolio_klip_schema_get
Get klip schema
klipfolio_klip_schema_update
Update klip schema
klipfolio_klip_update
Update klip
klipfolio_klips_list
List klips
klipfolio_profile_get
Get profile
klipfolio_user_dashboards_list
List user dashboards

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Klipfolio tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["klipfolio"], toolNames: [
    "klipfolio_dashboards_list",
    "klipfolio_dashboard_klips_add",
    "klipfolio_dashboard_share_rights_update"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Add the Monthly Bookings Klip to the Q4 Pipeline Review dashboard and share it with the Sales group" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["klipfolio"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Add the Monthly Bookings Klip to the Q4 Pipeline Review dashboard and share it with the Sales group" }],
  tools,
});

// Execute the tool call with the user's vaulted Klipfolio API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["klipfolio"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Add the Monthly Bookings Klip to the Q4 Pipeline Review dashboard and share it with the Sales group" }],
  tools,
});

// Tool call runs with the user's vaulted Klipfolio API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["klipfolio"] }, pageSize: 100,
});

const agent = new Agent({
  name: "reporting_agent",
  model: "gemini-2.5-pro",
  instruction: "Klipfolio tools scoped to this user",
  tools,
});

await agent.run("Add the Monthly Bookings Klip to the Q4 Pipeline Review dashboard and share it with the Sales group");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Klipfolio tool. Click to copy, paste into your agent, done.
Dashboards
Copy the prompt
Copied
Create a dashboard called Q4 Pipeline Review.
Copy the prompt
Copied
Add the Monthly Bookings Klip to the Q4 Pipeline Review dashboard.
Copy the prompt
Copied
Publish the Q4 Pipeline Review dashboard as a password-protected link.
Data sources
Copy the prompt
Copied
List the data sources I can access.
Copy the prompt
Copied
Refresh the Deals data source now.
Copy the prompt
Copied
Disable the Legacy Leads data source.
Sharing and comments
Copy the prompt
Copied
Share the Q4 Pipeline Review dashboard with the Sales group.
Copy the prompt
Copied
List the users in the Finance group.
Copy the prompt
Copied
Add a comment to the Monthly Bookings Klip about the October dip.
SEE HOW AUTH WORKS
Each user connects their own Klipfolio API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Klipfolio
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
Klipfolio
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
Klipfolio
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
Klipfolio
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 analytics and BI connectors.
GTM and RevOps Teams
Revenue forecast commentary
Pulls open pipeline from Salesforce and HubSpot, calculates coverage against quota, flags at-risk stages, posts commentary to Slack, and logs every snapshot to Google Sheets.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Test other agents
See the same per-user auth pattern across other analytics and BI connectors.
GTM
Revenue forecast agent
Score pipeline coverage against quota across Salesforce and HubSpot, post forecast commentary to Slack, log snapshots to Sheets.
GTM
Competitive intelligence briefing agent
Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Klipfolio API key looks fine in a demo. In production every dashboard change and share looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Klipfolio today. Ten connectors 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 Klipfolio as the user or through a shared key?
As the user. Each user connects their own Klipfolio API key once, and Scalekit sends it with every call. Audit logs attribute every dashboard change and share to that user, not a shared service account.
Where is the Klipfolio API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Klipfolio?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example dashboard and Klip read tools without klipfolio_dashboard_delete or klipfolio_datasource_delete, which delete permanently. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Klipfolio 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.
Does the Klipfolio connector work with client accounts?
Yes. klipfolio_clients_list and klipfolio_client_get read the client accounts a partner Klipfolio account manages, and the user and group tools can list users and groups in the company or in a client account.
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"": {
""klipfolio"": {
""url"": ""https://mcp.scalekit.com/klipfolio"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.klipfolio]
url = ""https://mcp.scalekit.com/klipfolio""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""klipfolio"": {
""url"": ""https://mcp.scalekit.com/klipfolio"",
""type"": ""http""
}
}
}