MCP Server for AI Coding Agents

Your AI agent writes code. It doesn't know what's happening around it.

When Claude Code, Cursor, or any AI agent works on a file, it doesn't know that 3 other people modified the same module this week. It doesn't know that a Slack thread decided on a different approach yesterday. It doesn't know that a review bottleneck is blocking everything in this area. Zamski's MCP server gives your agent the organizational context it's missing.

MCP integration showing a terminal with zamski_ask tool call and .mcp.json configuration file

15 tools. Every tool your agent needs to code with context.

Note: the API uses "situations" as the technical term for what we call ARCs.

Before you code

Check what is happening around the files you are about to modify.

zamski_file_context

Who else is working here? Are there open PRs, related tickets, active ARCs? Who is the domain expert?

zamski_work_item_context

Everything about a ticket: description, team comments, acceptance criteria, Slack decisions, PR feedback, meeting notes.

Understand the organization

Search across every platform your team uses.

zamski_search

Cross-platform search across Jira, GitHub, and Slack in one call.

zamski_ask

Natural language question routed through chain reasoning. Returns answers with sources, confidence, and reasoning steps.

zamski_find_experts

Who should review this change? Ranked experts with expertise scores and recent activity.

Know what matters

See the coordination landscape before making decisions.

zamski_situations

Active ARCs from the spatial radar, sorted by gravity. Pattern type, severity, signal count, kinetic state.

zamski_view_situation

Deep dive into a specific ARC. Narrative, spatial metrics, related signals.

zamski_intelligence_feed

Scored intelligence feed. Critical, high, medium, and low items with explanations and evidence.

zamski_brief

Daily intelligence brief. Top ARCs, alerts, personal metrics, sprint health.

Manage your work

Track what needs attention.

zamski_my_work

Your assigned PRs, tickets, calendar items, and items needing attention.

zamski_meeting_decisions

Recent meeting summaries with decisions and action items. What was decided in the last standup?

zamski_triage

Unclassified signals not yet linked to any ARC.

Take action

Create and link organizational context.

zamski_create_situation

Create an ARC when you spot a pattern the evaluators have not detected yet.

zamski_tag_situation

Link PRs, tickets, or commits to an existing ARC.

What changes when your agent has context

Before modifying a file

Without Zamski MCP
Agent reads the file, writes the code, opens a PR.
With Zamski MCP
Agent calls zamski_file_context(["src/auth/jwt.ts"]) Discovers: 2 open PRs already touch this file Discovers: @sarah is the domain expert (87% of recent commits) Discovers: Active "Coordination Gap" ARC in the auth module Discovers: Meeting decision from Tuesday: "use OIDC, not custom JWT" Agent warns the developer, follows the team decision, and suggests @sarah as reviewer.

Avoided a conflicting PR and followed the team decision automatically.

Implementing a ticket

Without Zamski MCP
Agent reads the Jira title and description. Implements based on that.
With Zamski MCP
Agent calls zamski_work_item_context("PLAT-312") Gets: Full ticket + 12 comments with design decisions Gets: Slack thread where the team debated the approach Gets: Meeting decision that narrowed scope to Phase 1 only Gets: Related PR #89 that was rejected for a similar approach Agent implements with full context. Follows Phase 1 scope. Avoids the approach that was already rejected.

Implemented correctly on the first attempt with full organizational context.

Morning standup

Without Zamski MCP
Developer opens four tabs, scans notifications, forgets half of them.
With Zamski MCP
Agent calls zamski_brief() 2 ARCs need attention (Review Bottleneck rising, Stale Work in your area) 1 PR needs your review (waiting 3 days) Sprint health: 72% completion, 3 days remaining No sentinel alerts Agent surfaces priorities. Developer walks into standup prepared.

Priorities surfaced in seconds instead of 15 minutes of tab-switching.

Install in 30 seconds

For Claude Code

Add to .mcp.json in your project root:

{
"mcpServers": {
"zamski": {
"command": "npx",
"args": ["@zamskiinc/mcp-server"],
"env": {
"ZAMSKI_API_URL": "https://api.zamski.com"
}
}
}
}

Then authenticate:

npx @zamskiinc/mcp-server auth login

For Cursor and other MCP-compatible agents

Same configuration. Any agent that supports the Model Context Protocol can connect.

Authentication options

1.

Interactive login (device code flow) for individual developers

2.

Access token (environment variable) for CI and automation

Not another code search plugin

Cross-platform context, not just code

Most agent plugins search code. Zamski searches Jira tickets, Slack threads, meeting decisions, calendar patterns, and code. The agent gets the full picture.

Organizational intelligence, not just data

zamski_ask doesn't return search results. It routes through chain reasoning with access to expertise models, cross-platform identity resolution, and ARC narratives. Answers include confidence scores and sources.

Coordination awareness

No other MCP plugin tells your agent "there is an active review bottleneck in this area" or "two other people are modifying related files this week." This is the gap between coding alone and coding as part of a team.

On the roadmap

01

Real-time ARC updates via WebSocket so agents get notified when coordination patterns change during long sessions

02

Proactive conflict detection that warns BEFORE you create a conflicting change

03

Embedding-based semantic code search to find patterns like "all error handling similar to this"

04

Review load balancing that suggests reviewers based on capacity and domain knowledge

05

Narrative history showing how a file participated in resolved ARCs over the last 90 days

Give your AI agent the context it's missing.

15 tools. One MCP server. All the organizational context your agent can't see on its own.

Install nowView on npm