Cognee connector for AI agents

Tools your memory agent reaches for on Cognee, scoped per user.

CALL ANY TOOL

Run agent memory end to end: recall from the knowledge graph, provision and inspect datasets, enrich them, and forget data on demand.

cognee_check_status

Check status

Check the processing status of Cognee datasets' pipelines. Use this to track an Improve run started with runInBackground=true, or to confirm ingestion/graph-building has completed before recalling.

Parameters

Name

Type

Required

Description

dataset

array

Optional

JSON array of dataset UUIDs to check (from List datasets). Omit to get status for all datasets you can read.

pipeline

array

Optional

JSON array of pipeline names to check: 'add_pipeline' or 'cognify_pipeline'. Omit to default to cognify_pipeline.

cognee_create_dataset

Create dataset

cognee_dataset_schema_update

Update dataset schema

cognee_forget

Forget

cognee_get_dataset_data_raw

Get dataset data raw

cognee_get_dataset_graph

Get dataset graph

cognee_get_dataset_schema

Get dataset schema

cognee_improve

Improve

cognee_list_dataset_data

List dataset data

cognee_list_datasets

List datasets

cognee_list_ontologies

List ontologies

cognee_ontology_delete

Delete ontology

cognee_recall

Recall

cognee_recall_history

Recall history

cognee_remember

Remember

cognee_remember_entry

Remember entry

cognee_skill_ingest

Skill ingest

cognee_visualize

Visualize

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

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);

// Cognee tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["cognee"], toolNames: [
    "cognee_recall",
    "cognee_list_datasets",
    "cognee_improve"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "What do we know about Acme Corp?" }] });

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: ["cognee"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Recall every decision about the pricing migration." }],
  tools,
});

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

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List all datasets and what each one contains." }],
  tools,
});

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

const agent = new Agent({
  name: "cognee_memory_agent",
  model: "gemini-2.5-pro",
  instruction: "Manage Cognee memory for the signed-in user.",
  tools,
});

await agent.run("Has the enrichment run on support_tickets finished?");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Cognee tool. Click to copy, paste into your agent, done.

Recall context

Copy the prompt

Copied

What do we know about Acme Corp's onboarding issues?

Copy the prompt

Copied

Recall every decision we logged about the pricing migration.

Copy the prompt

Copied

Search memory for past conversations that mention churn risk.

Manage datasets

Copy the prompt

Copied

List all datasets and their UUIDs.

Copy the prompt

Copied

Create a dataset called support_tickets for the new project.

Copy the prompt

Copied

Show me every item stored in the acme_support dataset.

Enrich and clean up

Copy the prompt

Copied

Run an improve pass over the support_tickets dataset.

Copy the prompt

Copied

Has the last enrichment run finished yet?

Copy the prompt

Copied

Forget the outdated 2024 roadmap dataset.

SEE HOW AUTH WORKS

Your users connect once. Their Cognee credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Cognee

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

Store

Their

Cognee

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

Resolve

When your agent calls a

Cognee

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

Audit

Every

Cognee

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 memory connectors.

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.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

Support and Ops Teams

Support triage agent

Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Cognee key looks fine in a demo. In production every recall, improve, and forget looks like one service account, and you cannot tell whose memory the agent touched. 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.

Cognee 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 Cognee 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 recall, enrichment, and deletion in your audit trail is attributed to a real user, not a shared service account.

Where is the Cognee API key stored?

In an AES-256 encrypted vault with per-tenant namespacing. Keys are resolved at request time, never enter LLM context, and can be revoked from one dashboard.

Can I limit what the agent does in Cognee?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example recall and list without improve or forget. 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.

Forget is permanent. What stops an agent from wiping memory?

Exclude cognee_forget from listScopedTools and the agent never sees the tool. If you do expose it, Scalekit still scope-checks every call before it reaches Cognee and logs exactly which user's agent deleted which dataset.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit