Server Configuration

MCP server endpoints are managed through the Agentic Skills page in the Graph Studio admin console. The left sidebar displays server cards; the main panel shows skills and configuration for the selected server. Changes take effect immediately — no restart required.

Managing Server Endpoints

Adding a server: Click the Add Server button (+ icon) in the sidebar header. Fill in the form and click Create.

Editing a server: Select a server card in the sidebar, open the Configuration tab, edit fields, and click Save.

Deleting a server: Click the delete icon on a server card and confirm. The default server cannot be deleted.

Server configuration fields:

Field	Description
Title	Display name shown in the sidebar and catalog
Description	Description of this server's purpose
Server Endpoint	Sub-path under /mcp (e.g., rest, services). Immutable after creation.
Skills Mode	Controls tool visibility and catalog scope (see below)
Enabled	Toggle the server endpoint on or of
Tools to Include	Whitelist patterns (e.g., rest_* general_sparqlClient). Supports * wildcards.
Tools to Exclude	Blacklist patterns (takes precedence over include list)
Server Instructions	Custom LLM system prompt injected into this server's MCP capabilities

Skills Mode

Each MCP server endpoint can be configured with a skills mode that controls two things independently:

1. Tool visibility — Which tools appear in the MCP tools/list response (i.e., what the LLM sees directly)
2. Catalog scope — Whether the skills catalog includes auto-grouped buckets for tools not explicitly defined in a skill, or only shows curated skills

Mode	Tool Visibility	Catalog Scope	Description
SKILLS_ONLY	Only skills_catalog visible. All other tools hidden but discoverable through the catalog.	Full — includes auto-grouped buckets for uncataloged tools.	Maximum token savings (~90%). LLM discovers all tools on demand.
SKILLS_CURATED	Only skills_catalog visible. Same as SKILLS_ONLY.	Curated only — no auto-grouped buckets. Only explicitly-defined skills appear.	Maximum token savings + full control. Uncataloged tools are not discoverable through the catalog, but remain callable via execute if the name is known.
ALL_TOOLS	All tools visible directly	Full — includes auto-grouped buckets for uncataloged tools.	Traditional mode. Catalog is a navigation aid, not a gate.

Key distinction — SKILLS_ONLY vs. SKILLS_CURATED:

• Both show only the skills_catalog tool in tools/list.
• In SKILLS_ONLY, hidden tools are still discoverable — the catalog auto-groups them into dynamic buckets, so the LLM can find and call them.
• In SKILLS_CURATED, the catalog only shows curated skills — uncataloged tools are not discoverable through the catalog, but remain callable via execute if the tool name is known.

When to use each mode:

• SKILLS_ONLY (recommended default) — The LLM can solve problems beyond what was anticipated. If a user asks something unexpected and an uncataloged tool can help, the LLM discovers it through auto-grouped dynamic buckets and uses it — no one needs to have predicted that use case. Best for systems like Graph Studio, where dozens of semantic services may be useful in unpredictable combinations.
• SKILLS_CURATED — The LLM can only do what was explicitly planned for. Use this when you’ve stabilized your tool set and want full control over what the LLM sees — for example, in a locked-down production deployment where predictability matters more than flexibility.
• ALL_TOOLS — Traditional MCP mode. All tools visible directly. The catalog is available as a navigation aid but provides no token savings.

Default configuration:

The default server ships with skillsMode=SKILLS_ONLY. You can change this by selecting the server in Agentic Skills, opening the Configuration tab, and editing the Skills Mode field.

Tool Filtering

The Tools to Include and Tools to Exclude fields on each server's configuration form optionally restrict which tools are available. Both support space-separated patterns with * wildcards (e.g., rest_* general_sparqlClient). Exclude patterns take precedence over include patterns. By default, no include filter is set — all registered tools are available through the skills catalog.

Multiple MCP Server Endpoints

You can run multiple MCP servers with different tool sets and skills modes. Add new servers using the Add Server button in Agentic Skills:

Server	Endpoint	Skills Mode	Tools Included	Tools Excluded
General purpose	/mcp/general	SKILLS_ONLY	all	–
Power users	/mcp/power	ALL_TOOLS	all	–
Read-only	/mcp/readonly	ALL_TOOLS	general_sparqlClient	*_delete* *_create*

Server configurations are stored in the journal and take effect immediately — no server restart required.

Per-Server Skills Catalogs

Each MCP server endpoint can have its own independent skills catalog in addition to its own skills mode. This allows different server endpoints to expose different sets of skills.

• By default, all servers share the same skills catalog
• Skills edited through the Agentic Skills admin page or REST API update the default catalog
• Once you add, modify, or copy a skill to a specific server, that server gets its own independent catalog and stops inheriting from the shared one
• To go back to using the shared catalog, click Reset to Defaults on that server's Skills tab