How it works Teams Dashboard
Get started free
for teams building with agents

The context exists.
Your agent just can't reach it.

Your team's decisions, patterns, and hard-won lessons - scattered across sessions and people. Splicr closes the gap. Every agent, every session, the full picture.

Get started free →
# install + configure all your agents in 60 seconds
npx @splicr/mcp-server setup click to copy
Detected: Claude Code, Cursor
Configuring MCP server... done
Injecting context hooks... done
Ready. Your agents now have memory.
# last session, your agent decided on JWT refresh tokens
# new session - working on a related auth flow...
> add token refresh to the mobile API client
splicr - get_relevant_context
1. [DECISION] "JWT refresh token rotation pattern"
"Must revoke old token server-side before issuing
new one, or you're vulnerable to replay attacks"
auto-extracted 5d ago | used 3x
Your agent already knows what it decided last week.
No repeating yourself. The context just arrived.
# your co-founder's agent hit a deploy bug on Monday
# Splicr auto-extracted the workaround
# Thursday - you're working on the same pipeline
> fix the Cloudflare Pages redirect issue
splicr - get_relevant_context
1. [ANTI-PATTERN] "Cloudflare pretty URLs strip path segments"
"Use query params instead of path rewrites for
redirects. Pretty URLs silently break paths."
from teammate's session 3d ago
You never asked. They never shared.
The knowledge just arrived.
# new engineer joins the team - day 1
# their agent bootstraps from 3 months of team knowledge
splicr - get_project_context
Active patterns for this project:
1. "Use Zod for all input validation" pattern
2. "JWT over session cookies for cross-service auth" decision
3. [ANTI-PATTERN] "Don't use bull queue for simple retries" failure
47 decisions, 12 anti-patterns, 8 workarounds loaded.
New engineer's agent is smart from session one.
npx @splicr/mcp-server setup copy
The problem
What's actually happening right now
▦

Inconsistent choices

Agent A picks Zod. Agent B picks Joi. Agent C picks Yup. Nobody knows until code review. Multiply by every dev, every session, every day.

⚠

Repeated mistakes

Someone tried Redis for session storage. It didn't scale. Three weeks later, another agent suggests Redis for session storage.

●

Lost context

Your agent solved this exact bug last Tuesday. Your teammate's agent discovered a workaround last week. None of it reaches today's session.

Code tells you how. Git tells you what changed. Nothing tells your agent why.

How Splicr works
The context layer your agents are missing
Decisions and discoveries auto-extract from every session. AI routes them to the right projects. Your agents start every session informed.

Agents generate knowledge

Every session, your agents make decisions, discover workarounds, and learn patterns. Splicr auto-extracts these learnings - no manual effort. The knowledge builds itself.

auto-extracted from sessions
Session: auth service refactor
[DECISION] "Chose HNSW over IVFFlat for pgvector" extracted
Session: deploy pipeline fix
[ANTI-PATTERN] "Don't use memory store in prod" extracted
Session: API rate limiting
[PATTERN] "Sliding window over fixed window" extracted

AI distills and routes

Every learning is distilled into a structured insight, tagged by type (decision, pattern, failure), and routed to the right projects automatically. No folders. No manual organization.

AI pipeline
Session ended: auth service refactor (47 tool calls)
Extracted: "Chose JWT over session cookies
for cross-service auth (mobile can't maintain cookies)"
Type: decision | Confidence: high | Durability: permanent
Routed: auth-service (92%), mobile-app (67%)

Agents start informed

Before your agent writes a single line of code, it already knows what your team knows. Decisions, patterns, anti-patterns - injected silently at session start.

Claude Code
> add rate limiting to the API endpoints
splicr - get_relevant_context [task + branch + files]
1. "Rate limiting patterns for APIs"
"Use sliding window, not fixed window. Token
bucket for burst, sliding window for sustained."
extracted 2d ago | used 3x
2. [ANTI-PATTERN] "express-rate-limit memory store leaks"
"Don't use default memory store in production."
from teammate's session 1w ago
The compound effect
It doesn't just store knowledge. It compounds it.
01

Agent works

Makes decisions, discovers patterns

02

Splicr extracts

Decisions, patterns, failures auto-captured

04

Loop compounds

Next session is smarter

03

Context surfaces

Injected at next session start

→
↓
←
↑

Session 1

Agent starts from zero

Session 30

47 decisions, 12 anti-patterns, 8 workarounds

Every session makes the next one smarter. Every teammate makes the whole team smarter.

The team multiplier
Knowledge transfers without communication

Two developers. Same codebase. They never talk about this problem.

A
Dev A Monday
Working in Claude Code. Hits a Cloudflare Pages bug - pretty URLs strip path segments during redirects.
Claude Code
Figured out the workaround:
Use query params, not path rewrites.
✓ Auto-saved to Splicr [decision]
Dev A moves on. Never mentions it.
3 days later
B
Dev B Thursday
Working in Cursor on the same deploy pipeline. Agent starts the session and Splicr injects the answer automatically.
Cursor
splicr - get_relevant_context
[ANTI-PATTERN]
"Pretty URLs strip path segments"
Use query params instead of path rewrites.
from teammate 3d ago
Dev B never asked. The knowledge just arrived.

The 90% of decisions too small to document but too valuable to forget - transferred automatically between people who never communicated.

One context layer. Every agent.

Splicr speaks MCP. Any agent that supports it gets your team's full context automatically.

1,200+
decisions extracted
400+
agent sessions

"My agent hit the same auth problem a week later. Didn't even search - Splicr injected the decision from last session before I typed anything."

solo dev

"We stopped getting inconsistent patterns across sessions. One agent decides, every future session knows."

solo dev

"My co-founder's agent discovered a deploy workaround. Three days later my agent warned me about the same issue. We never even discussed it."

2-person team
free during beta - everything unlocked
One command. Every agent. Start now.

Run this in your terminal. Authenticate, auto-detect your agents, done.

npx @splicr/mcp-server setup click to copy
# create a team
npx @splicr/mcp-server team create "My Team" click to copy
# teammate joins + sets up in one command
npx @splicr/mcp-server setup --join <invite-code> click to copy