IGPT MCP

Live

OAUTH 2.1

KNOWLEDGE SEARCH

AI

IGPT MCP gives agents authenticated access to your connected datasources: search documents and messages, or ask a question and get an answer grounded in your data.

  • 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.
IGPT MCP
agent · Acme Q3
Run
What did the team decide about the pricing page redesign?
S
igptmcp_ask
210ms
IGPT agent
Team decided to ship the simplified 3-tier pricing page, per the Oct 14 planning doc.
Sources: 2 documents, 1 message thread
igptmcp
2 sources
18:29
Message Claude...

Tools your knowledge agent reaches for on IGPT, scoped per user.

CALL ANY TOOL
Search and ask across connected documents and messages, scoped to each user's own IGPT datasources.
igptmcp_ask
Ask records
Send a user question to IGPT and return an answer based on connected datasources, which include documents and messages.
Parameters
Name
Type
Required
Description
input
string
Required
User input question.
output_format
string
Optional
"json" for a generic object, or a JSON Schema to enforce a specific output structure.
igptmcp_search
Search records
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);

// IGPT tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["igptmcp"], toolNames: [
    "igptmcp_ask",
    "igptmcp_search",
    "igptmcp_ask"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "What did the team decide about the pricing page redesign?" }] });
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: ["igptmcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "What did the team decide about the pricing page redesign?" }],
  tools,
});

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

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "What did the team decide about the pricing page redesign?" }],
  tools,
});

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

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

await agent.run("What did the team decide about the pricing page redesign?");
Try these prompts
Copy any prompt into your agent. Each maps directly to a IGPT MCP tool. Click to copy, paste into your agent, done.
Ask your data
Copy the prompt
Copied
What did the team decide about the pricing page redesign?
Copy the prompt
Copied
Summarize what was said about the Q4 roadmap.
Copy the prompt
Copied
Ask what the blocker was on the auth migration.
Search records
Copy the prompt
Copied
Search for mentions of 'pricing page' from the last month.
Copy the prompt
Copied
Find documents referencing the vendor security review.
Copy the prompt
Copied
Search messages about the outage from last week.
Recency and structure
Copy the prompt
Copied
Show the most recent records with no query, newest first.
Copy the prompt
Copied
Ask for the answer as structured JSON with a summary field.
Copy the prompt
Copied
Search records between 2026-06-01 and 2026-06-30.
SEE HOW AUTH WORKS
Your users connect once. Their IGPT MCP credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
IGPT 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
IGPT 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
IGPT 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
IGPT 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 AI and knowledge-search connectors.
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.
Support and Ops Teams
Support ticket automation agent
Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.
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.
Support and Ops Teams
Email-to-calendar agent
Reads scheduling intent out of Gmail threads, resolves the times everyone actually has free, and creates the event on the user's own Google Calendar. No shared service account.
Test other agents
See the same per-user auth pattern across other AI and knowledge-search connectors.
OPS
Email-to-calendar scheduling agent
Read scheduling intent out of Gmail threads, resolve mutual free time, and create the Google Calendar event.
SUPPORT
Support ticket automation (Google ADK)
Fetch, annotate, and archive Zendesk tickets with Notion context, digesting anything it cannot answer 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.
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.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared IGPT MCP token looks fine in a demo. In production every search query 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 token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
IGPT MCP 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 IGPT MCP 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 IGPT MCP action in your audit trail is attributed to a real user, not a shared service account.
Where is the IGPT MCP 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 IGPT MCP?
Yes. Filter by tool name in listScopedTools to expose only what you want. 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.
Does the agent see every document in the workspace, or only what the user can see?
Only what the user can see. IGPT resolves search and ask against the datasources the authenticated user has access to, so results never leak content from datasources outside that user's permissions.
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"": {
""igptmcp"": {
""url"": ""https://mcp.scalekit.com/igptmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.igptmcp]
url = ""https://mcp.scalekit.com/igptmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""igptmcp"": {
""url"": ""https://mcp.scalekit.com/igptmcp"",
""type"": ""http""
}
}
}