cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
Claude Code
Syndu For Claude Code
← Back to platform brief
Claude Code

Syndu For Claude Code

Connect Claude Code to Syndu's hosted MCP surface so recurring engineering, security, fraud, and abuse work can inherit outside-in risk context, live community-demand cues, governed workspace memory, and access your workspace owns instead of starting fresh every time.

Open Access Dashboard Open MCP page Pricing
Claude Code setup

Add Syndu to Claude Code with one hosted MCP entry

Create the workspace MCP credential in your Syndu workspace Access Dashboard first, then run this in the shell where you use Claude Code. The same workspace key keeps Claude Code inside access your workspace owns across retries, restarts, and future sessions until you rotate it.

export SYNDU_MCP_TOKEN="<create this in Access Dashboard>"
claude mcp add --transport http syndu https://syndu.com/mcp \
  --header "Authorization: Bearer ${SYNDU_MCP_TOKEN}"
Create the key in the Access Dashboard Add the hosted server once Reuse the same workspace memory Open Plans if quota runs out
Documentation index Platform brief Quota rules Privacy FAQ
Hosted endpoint
https://syndu.com/mcp/

Claude Code connects to Syndu as one hosted MCP surface, so there is no local bridge to maintain.

Workspace credential
Create the key in the Access Dashboard

The Syndu workspace Access Dashboard is where the operator creates the workspace MCP credential Claude Code will send as the bearer token. That is what turns the connection into owned workspace access.

Memory model
Keep approved conclusions

Claude Code can preserve approved findings in workspace memory so future runs inherit the same risk posture and case state.

Live analyst demand
10-minute queryability signal

Claude Code can see when the same entity is being queried repeatedly across the public surface, with recent windows and requester convergence exposed as a fresh investigative clue.

Quota handoff
/access/?mode=mcp&reason=quota#plans

When the daily metered investigation budget runs out, return to the Access Dashboard and expand the same owned workspace access instead of starting over elsewhere.

What Claude Code Gets

Claude Code should feel like a persistent operator, not a disposable shell. Syndu adds outside-in investigation context and a governed place to keep the approved answer.

Operator loop

Investigate without leaving the terminal workflow

Use the hosted Syndu MCP server when Claude Code needs a report-backed answer on a risky identifier and the next action depends on clear context.

Resolve risky identifiers Explain why they matter Preserve the approved conclusion
Shared memory

Keep the answer for the next run

Workspace memory lets Claude Code inherit the last approved conclusion instead of rebuilding the same case context in every new session.

Governed workspace storage Share-safe hive contribution when allowed Same quota and memory model as the rest of Syndu

Why Claude Code Teams Use Syndu

The product value is not just an MCP connection. It is that Claude Code can investigate, preserve, and reuse conclusions in the same workspace memory system the rest of Syndu already uses.

Claude Code

One hosted MCP server, not a local bridge

Claude Code points at Syndu's hosted MCP endpoint directly, so setup stays light and the team can standardize on one shared operating surface.

Claude Code

Outside-in risk context where code and operations meet

Use Claude Code when a task touches risky IPs, domains, organizations, or related identities and you want outside-in evidence without opening a second tool chain.

Claude Code

Approved outcomes survive the shell

Syndu turns a one-off Claude Code run into reusable team knowledge by preserving approved outcomes in governed workspace memory.

Claude Code

Fresh community attention reaches the terminal loop

The same Claude Code lookup can now carry Syndu's live community-demand signal, so the operator can see whether multiple analysts are converging on the entity right now instead of relying only on slower published rollups.

Claude Code

Quota stays workspace-bound

The Claude Code connection does not create a separate quota universe. Metered investigation calls belong to the same workspace and return to the Access Dashboard when the budget needs to be expanded.

Claude Code Setup Flow

The practical flow is simple: identify the workspace, create one MCP credential, add the hosted server, then work as normal.

01

Open the Access Dashboard MCP controls

Sign into Syndu and open the Access Dashboard MCP panel for the workspace you want Claude Code to use.

02

Create one workspace MCP credential

Generate the credential in the Access Dashboard and keep it ready for the shell where Claude Code runs.

03

Add Syndu as a hosted MCP server

Run the add command once with the bearer header pointing at the exported workspace key.

04

Investigate, explain, preserve

Use Claude Code with Syndu when the task needs live risk context and keep the approved outcome in workspace memory for the next run.

Related Resources

Documentation

Syndu Documentation Index

Syndu gives computer-using agents governed memory, shared workspace context, and specialized cyber intelligence when the workflow needs it. This index maps the two plugin tracks, the hosted cyber MCP workflows, the Risk API, pricing, privacy, and the evidence depth behind the system.

4 briefing points Documentation
Open article
Coverage

What Syndu Reports Cover

Syndu exposes a dimensional risk surface across network entities and geography: ip address, subnet, ISP, ASN, organization, city, region, and country. That same dimensional graph powers the Risk API, MCP tools, and the memory loop that preserves the resulting decisions.

4 briefing points Coverage
Open article
Operations

Using Syndu with SoC and SIEM Workflows

Syndu is an external context layer for monitoring, hygiene review, agent workflows, and decision support. It complements SoC and SIEM processes rather than replacing them, while sharing the same evidence and memory model used elsewhere on the platform.

4 briefing points Operations
Open article
Fraud operations

Using Syndu with Fraud, Payments, and Merchant-Risk Workflows

Syndu is also a decision surface for fraud, payments, merchant-risk, and trust workflows. The same outside-in evidence graph, Risk API, and governed memory loop help teams score, review, and preserve conclusions around risky identifiers.

4 briefing points Fraud operations
Open article
AI and scale

Consuming Syndu at Scale

The platform supports three access surfaces at scale: direct report access for large-scale browser or agent consumption, the Risk API for application-native scoring, and the MCP server for collaborative agent workflows.

4 briefing points AI and scale
Open article
Delivery modes

Direct, API, and MCP Access

Syndu is one platform with three access surfaces: direct access for report-shell consumption, API access for application-side scoring, and MCP access for agent collaboration. They sit under the same workspace, quota, and subscription control plane, but differ in delivery contract.

4 briefing points Delivery modes
Open article
Register

Create a workspace to govern access to Syndu.

Registration unlocks the workspace control plane, plan selection, credential provisioning, and the subscription flow across web, API, and MCP access.

Register Sign in to workspace