SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Past.dev MCP with Atomic Agent

Connect Atomic Agent to Past.dev MCP. Recall product decisions from last quarter, inspect memory traces for recent requests, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Past.dev logoPast.dev
Api Key

Past.dev is a source-backed memory service for AI agents. It helps agents retain, trace, and safely manage durable context.

29 Tools

Introduction

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Past.dev.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Past.dev account. See the Atomic Agent documentation for installation instructions.

Also integrate Past.dev with

ChatGPTClaude CoworkHermes

How Atomic Agent connects to Past.dev

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect Past.dev to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in Past.dev. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your Past.dev account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the Past.dev MCP server, and what's possible with it?

The Past.dev MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Past.dev account. It provides structured and secure access to durable, source-backed memory, identities, audiences, usage data, diagnostics, and request history, so your agent can store and recall memories, manage identity access, diagnose ingestion, and inspect or clean up memory on your behalf.

  • Durable memory ingestion and recall: Have your agent store timestamped information, ingest memory in batches, and recall ranked, source-backed context for an identity.
  • Identity and audience management: Let the agent create, update, list, or remove identities and organize access with fixed or trait-based audiences.
  • Ingestion diagnostics: Direct your agent to estimate ingestion costs, check processing status, explain partial or failed ingestions, and retry eligible work.
  • Usage and activity monitoring: Instruct your agent to review credit usage, inspect API request history, and analyze request counts over selected time periods.
  • Memory lineage and cleanup: Have your agent trace how memories and source information relate over time, inspect timeline details, and permanently delete selected memory data when needed.

Use Past.dev from Atomic Agent

With your account connected, ask Atomic Agent to work with Past.dev in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

TOOLS

Supported Tools

Every Past.dev action and event your agent gets out of the box.

Replace Identities in Bulk

Atomically create or replace complete trait sets for up to 1,000 identities; omitted traits replace the identity with no traits.

Delete Audience

DESTRUCTIVE ACCESS CHANGE: Permanently delete an audience.

Delete Identity

DESTRUCTIVE: Permanently delete an identity directory record and remove it from every audience.

Permanently Delete Ingestion Memory

DESTRUCTIVE: Permanently delete every data point accepted by one ingestion and memory depending only on those points.

Delete Memory Data Point

DESTRUCTIVE: Permanently delete one data point by its caller-owned source id and remove memory derived from it.

Delete Memory Data Points

DESTRUCTIVE: Permanently and atomically delete up to 1,000 data points by caller-owned source id and remove memory derived from them.

Estimate Ingestion

Cut files into data points, plan batches, and estimate credits without storing data or spending credits.

Explain Ingestion

Diagnose how far one send progressed, including per-item searchability, memory counts, failure details, and the recommended next step.

Find Trace Roots

Find memory and source nodes for lineage or timeline inspection, returning independent memory and source cursors.

Get Audience

Read one fixed, rule, or default audience with its definition and current membership and memory counts.

Get Identity

Return one identity's traits, origin, timestamps, and current audience memberships.

Get Ingestion Status

Poll one ingestion for processing, completion, failure, and project readiness without consuming metered request quota.

Get API Request

Read one API call and its retained allowlisted headers and request/response payload; bearer credentials are never returned.

Get Request Histogram

Count accepted, failed-later, and rejected API calls in provider-selected time buckets using request-log filters.

Get Trace Lineage

Read what a memory or source was built from and what was built on it, including graph edges and hidden-node count.

Get Trace Node

Read one memory or source node with revision, validity, replacement, request, content, and graph counts.

Get Trace Timeline

Read rooted source and memory work, ingestions, recalls, and supersessions on a clock for a window of at most 31 days.

Get Usage

Return the current UTC month's credit balance, metering state, and project ingestion, recall, and cap usage.

Ingest Memory

Ingest one timestamped data point into durable memory, optionally associating it with an identity and audience; reusing an id replaces the prior revision when stored fields change.

Ingest Memory Batch

Atomically ingest 1 to 1,000 ordered memory data points in one request, avoiding fragile per-item agent loops.

List Audiences

List every audience in the connected project, including the default project audience and current membership and memory counts.

List Identities

List project identities newest first, optionally filtering by one trait, and return a cursor for the next page.

List API Requests

List the connected project's API calls newest first, with filters and a cursor for the next page.

Recall Memory

Return ranked, source-backed memory visible to an identity for a query, with optional time range, sort order, and evidence budget controls.

Recompute Audience

Recompute an audience's membership from its definition and apply the refreshed access set to recall immediately.

Create or Replace Audience

Create or completely replace a fixed-list or trait-rule audience and its access definition.

Replace Identity

Create an identity or replace its complete trait set; omitted or empty traits remove all existing traits.

Retry Ingestion

Retry a stopped or failed ingestion under its existing id without spending additional credits; completed ingestions are rejected.

Update Identity Traits

Merge selected identity traits while preserving unspecified keys; set a trait value to null to remove that key.

FRAMEWORKS

How to build Past.dev MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Past.dev MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Past.dev MCP with Claude Cowork

Hermes logo

Hermes

Use Past.dev MCP with Hermes

FAQ

Frequently asked questions

With a standalone Past.dev MCP server, the agents and LLMs can only access a fixed set of Past.dev tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Past.dev and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Atomic Agent fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Past.dev tools.

Yes, absolutely. You can configure which Past.dev scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Past.dev data and credentials are handled as safely as possible.

Start with Past.dev.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Past.dev tool your agent needs.Free to start.

Start building