Sleekplan MCP

Live

OAUTH 2.1

PRODUCT FEEDBACK

Productivity

Sleekplan MCP gives agents authenticated access to your product feedback: triage requests, merge duplicates, publish changelogs, and summarize surveys.

  • Per-user credentials: each call uses the actual user's token, 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.
Sleekplan MCP
agent · Acme Q3
Run
What are the top feature requests this month, and are any of them duplicates?
S
sleekplanmcp_list_feedback
88ms
Sleekplan agent
Top 3 by votes: SSO support (142), dark mode (97), CSV export (63). Two dark mode posts look like duplicates; merging combines 31 votes into one thread.
Sources: 48 posts, 3 topics, Jul 1 to Jul 28
sleekplanmcp
48 posts
18:29
Message Claude...

Tools your product agent reaches for on Sleekplan, scoped per user.

CALL ANY TOOL
Run the full feedback loop: list and triage posts, merge duplicates, surface topics, publish changelogs, and read survey results.
sleekplanmcp_list_feedback
List feedback posts
List feedback posts with optional filtering and sorting by status, type, tag, segment, or owner. Supports full-text search and vote-based sort orders like trend and top.
Parameters
Name
Type
Required
Description
search
string
Optional
Full-text search query.
filter
string
Optional
Status key filter such as 'planned', a comma-separated list, or 'all'.
type
string
Optional
Feedback type key such as 'feature' or 'bug', a comma-separated list, or 'all'.
sort
string
Optional
Sort order: 'trend', 'top', 'new', 'priority', 'eta', and more.
per_page
integer
Optional
Number of results per page.
sleekplanmcp_create_feedback
Create feedback post
sleekplanmcp_get_feedback_stats
Get post stats
sleekplanmcp_merge_feedback
Merge duplicates
sleekplanmcp_list_topics
List feedback topics
sleekplanmcp_create_changelog
Publish changelog entry
sleekplanmcp_get_survey_summary
Summarize survey results
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);

// Sleekplan tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["sleekplanmcp"], toolNames: [
    "sleekplanmcp_list_feedback",
    "sleekplanmcp_get_feedback_stats",
    "sleekplanmcp_create_changelog"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "What are the top feature requests this month?" }] });
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: ["sleekplanmcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Which feedback posts are trending this week?" }],
  tools,
});

// Execute the tool call with the user's vaulted Sleekplan credential
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: ["sleekplanmcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Merge the duplicate dark mode requests into one post." }],
  tools,
});

// Tool call runs with the user's vaulted Sleekplan credential
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: ["sleekplanmcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "sleekplan_feedback_agent",
  model: "gemini-2.5-pro",
  instruction: "Triage Sleekplan feedback for the signed-in user.",
  tools,
});

await agent.run("How did people answer the onboarding survey?");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Sleekplan tool. Click to copy, paste into your agent, done.
Triage feedback
Copy the prompt
Copied
What are the top feature requests this month by votes?
Copy the prompt
Copied
List all bug reports still in the planned status.
Copy the prompt
Copied
Find duplicate posts about dark mode and merge them.
Ship the changelog
Copy the prompt
Copied
Draft a changelog entry for the new SSO release.
Copy the prompt
Copied
Schedule the v2.4 changelog for Monday 9am and notify subscribers.
Copy the prompt
Copied
List every changelog entry still sitting in draft.
Read the signal
Copy the prompt
Copied
Which feedback topics are growing fastest?
Copy the prompt
Copied
How did people answer the onboarding survey?
Copy the prompt
Copied
Get vote stats for the CSV export request.
SEE HOW AUTH WORKS
Your users connect once. Their Sleekplan credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Sleekplan 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
Sleekplan 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
Sleekplan 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
Sleekplan 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 feedback and survey connectors.
SUPPORT
Support triage agent
Read Zendesk tickets, fetch runbooks from Notion, and route to the right Slack channel with a drafted response.
SUPPORT
Support ticket automation (Google ADK)
Google ADK agent that classifies Zendesk tickets, pulls Notion context, and posts to Slack. End-to-end ticket handoff.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.
01.
Shared tokens break per-user analytics
A shared Sleekplan token looks fine in a demo. In production every merged post and published changelog looks like one service account, and you cannot tell who closed a request or shipped an announcement. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Sleekplan 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 Sleekplan as the user or through a shared key?
As the user. Scalekit resolves the credential of the person who triggered the agent at request time, so every merged post, status change, and changelog entry in your audit trail is attributed to a real user, not a shared service account.
Where is the Sleekplan token stored?
In an AES-256 encrypted vault with per-tenant namespacing. Tokens are resolved at request time, never enter LLM context, refresh automatically, and can be revoked from one dashboard.
Can I limit what the agent does in Sleekplan?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example read-only triage without merge, delete, or changelog publishing. Scalekit also enforces scope checks before every API call.
What happens when a user revokes access?
The credential is invalidated at the next tool call. The call fails closed, other users' connections are unaffected, and the revocation is logged in the audit chain.
Can the agent publish a changelog entry to customers by accident?
Only if you allow it. Keep create_changelog out of the scoped tool list for drafting agents, or have the agent pass draft=true so entries land unpublished for human review. Every publish call is scope-checked and logged either way.
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"": {
""sleekplanmcp"": {
""url"": ""https://mcp.scalekit.com/sleekplanmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.sleekplanmcp]
url = ""https://mcp.scalekit.com/sleekplanmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""sleekplanmcp"": {
""url"": ""https://mcp.scalekit.com/sleekplanmcp"",
""type"": ""http""
}
}
}