MCP is how an agent gains capabilities it doesn't have natively (a service, a database, an internal API). korgex is MCP-native — it can both consume servers and act as one.

Connecting an existing server (most common)

korgex mcp catalog to see curated presets; korgex mcp add <alias> [--global] to add one. For a custom server: --command <cmd> --args "…" (stdio) or --url <url> --header "Authorization: Bearer ${TOKEN}" (remote).
Put secrets in env and reference them as ${VAR} in the config — never inline a token.
korgex auto-connects configured servers at startup; tools appear namespaced as server__tool.

Authoring a server

Decide the tools: each gets a name, a one-line description (this is what the model sees), and a JSON-Schema inputSchema. Keep each tool single-purpose.
Implement the protocol: handle initialize → tools/list → tools/call over JSON-RPC (stdio or HTTP). Return results as content blocks; surface tool faults as an error result, not a crash.
Validate inputs at the boundary and treat all args as untrusted (see security-review). Don't expose destructive operations without a guard.
Test the handler purely (feed it requests, assert responses) before wiring a host.
Register it with korgex mcp add and confirm tools list + a sample call work.

Más de este repositorio

mismo repositorio

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

data-pipelines

New1Direction/korgex

Build reliable, resumable data connectors and transforms (ETL)

2026-06-015

name	building-an-mcp-server
description	Author or connect a Model Context Protocol server so an agent gains new tools
version	1
trust	built-in

MCP is how an agent gains capabilities it doesn't have natively (a service, a database, an internal API). korgex is MCP-native — it can both consume servers and act as one.

Connecting an existing server (most common)

korgex mcp catalog to see curated presets; korgex mcp add <alias> [--global] to add one. For a custom server: --command <cmd> --args "…" (stdio) or --url <url> --header "Authorization: Bearer ${TOKEN}" (remote).
Put secrets in env and reference them as ${VAR} in the config — never inline a token.
korgex auto-connects configured servers at startup; tools appear namespaced as server__tool.

Authoring a server

Decide the tools: each gets a name, a one-line description (this is what the model sees), and a JSON-Schema inputSchema. Keep each tool single-purpose.
Implement the protocol: handle initialize → tools/list → tools/call over JSON-RPC (stdio or HTTP). Return results as content blocks; surface tool faults as an error result, not a crash.
Validate inputs at the boundary and treat all args as untrusted (see security-review). Don't expose destructive operations without a guard.
Test the handler purely (feed it requests, assert responses) before wiring a host.
Register it with korgex mcp add and confirm tools list + a sample call work.