// MCP TOOL REFERENCE

CORE TOOLS

9 tools from the Core MCP Server, categorised by risk level.

View the Core policy → Token cost: 2,243 tokens →

// ALL 9 CORE TOOLS

READ 6 tools

Read memory_about_user Get user's profile information (background, preferences, work, interests). USE THIS TOOL: At the start of c... Read get_integration_actions Get list of actions available for a specific integration. USE THIS TOOL: After get_integrations to see what... Read get_integrations List all connected integrations (GitHub, Linear, Slack, etc.). USE THIS TOOL: Before using integration acti... Read memory_get_space Get detailed information about a specific space including its full summary. USE THIS TOOL: When working on ... Read memory_get_spaces List all available memory spaces (project contexts). USE THIS TOOL: To see what spaces exist before searchi... Read memory_search Search stored memories for past conversations, user preferences, project context, and decisions. USE THIS T...

WRITE 2 tools

Write initialize_conversation_session Initialize a session for this conversation. MUST be called FIRST at the start of every conversation before ... Write memory_ingest Store conversation in memory for future reference. USE THIS TOOL: At the END of every conversation after fu...

EXECUTE 1 tools

Execute execute_integration_action Execute an action on an integration (fetch GitHub PR, create Linear issue, send Slack message, etc.). USE T...

// RUNNING THIS SERVER

The managed route: connect Core through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @transcend-io/mcp-server-core

// FAQ

How many tools does the Core MCP server have? +

The Core MCP server exposes 9 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Core tools? +

Route the Core server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Core tools fall into? +

Core tools are categorised as Read (6), Write (2), Execute (1). Each category has a recommended default policy.

Enforce policy on every Core tool call.

Start from Core, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.