Developer platform
Stop rebuilding the same backend for every idea.
Your user's Pod already holds their data, identity, permissions, and history. Build on it with @synap-core/sdk, the full tRPC API, and scoped API keys — and connect any MCP agent to the same world through the Synap CLI.
Up and running in minutes.
- Get a pod. A hosted Data Pod, or your own with Docker Compose.
- Create an API key on your pod and choose its scopes.
- Install the SDK — TypeScript, fully typed.
npm install @synap-core/sdk - Start building. Query entities, search, create automations.
import { createSynapClient } from "@synap-core/sdk";
const synap = createSynapClient({
podUrl: "https://your-pod.synap.live",
apiKey: "synap_user_...",
workspaceId: "ws_...",
});
// Query entities
const notes = await synap.entities.list.query({
profileSlug: "note",
limit: 20,
});
// Search
const { entities } = await synap.entities.search.query({
query: "project apollo proposal",
});
// Create an entity
const task = await synap.entities.create.mutate({
profileSlug: "task",
title: "Write lightpaper",
properties: { status: "in-progress", dueDate: "2026-04-01" },
});Connect the agent you already use.
The Synap CLI writes the MCP config for your client and signs it in to your pod. Web clients like claude.ai and ChatGPT use the Synap Cloud connector instead.
Install the CLI and sign in:
npm install -g @synap-core/cli && synap loginPick a client to connect:
synap mcp connectOr paste the Cloud connector URL into a web client:
https://api.synap.live/mcpWhat you can build.
@synap-core/sdk
TypeScript client for the pod's full tRPC API, typed end to end. Works in Node.js and the browser.
API keys
Granular scopes for entities, relations, Hub Protocol, MCP and more. Bcrypt-hashed and revocable.
Hub Protocol
Open REST contract for agents and intelligence services, covering the pod's data operations. Implement it to connect any system.
MCP server
Your pod exposes a Model Context Protocol server. Any MCP-compatible client can read and write your data, under your governance.
Custom Cards
Build components that render anywhere in Synap Browser: panels, dashboards, documents, whiteboards. Sandboxed iframe with a postMessage SDK. Publish them to the Marketplace from the CLI with synap market publish.
Packages
Workspace, capability and Card packages install into any Pod. A workspace package carries its entity profiles, views and automations. Publish yours to the Marketplace.
Granular scopes.
API keys grant only the permissions you choose. Read access to entities doesn't imply write access. A few of the scopes a key can carry:
- read:entities
- write:entities
- relations
- knowledge_facts
- data.read
- data.write
- hub-protocol.read
- hub-protocol.write
- mcp.connect
- mcp.read
- mcp.write
- skills.invoke
- chat.stream
- webhook:manage
- realtime:observe