Build an MCP server or API integration

Compare developer workflows by language, protocol, tool schema, authentication, testing, and deployment boundary.

Last meaningful review July 20, 2026

The job

You need to build code that exposes or connects an existing service through MCP or an API integration.

IncludedMCP tool and server design · API client or integration scaffolding · integration tests and documentation

Not this pageno-code cross-SaaS reporting · credential-governance policy · production deployment approval

30-second route

You are building a new MCP server over an existing external API or service.

It explicitly covers API planning, authenticated infrastructure, schema design, testing, and evaluations.

Editorial confidence: high

Consider Mcp Builder ↗

The MCP server must be configured or bundled in a Claude Code plugin.

It provides plugin configuration, transport, auth, lifecycle, security, and local testing guidance.

Editorial confidence: high

Consider Mcp Integration ↗

You want a compact Node/TypeScript pattern for server primitives and local-versus-remote transport.

It explicitly covers TypeScript SDK setup, Zod schemas, MCP primitives, and Streamable HTTP.

Editorial confidence: high

Consider Mcp Server Patterns ↗

The primary goal is adding a conventional connector to an existing repository rather than exposing MCP.

The selected MCP skills are not the primary fit for a repository-native non-MCP connector.

Editorial confidence: medium

Adapt the host repository’s connector pattern.

Before you install

Install a selected Skill.

Each selected candidate directly supports building or integrating MCP/API services with explicit source-backed workflows; choose by implementation surface and language.

Read the intervention guide →

Source-led comparison

What changes the choice

Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.

SkillBest forActionEdits?Setup

Mcp BuilderBuilding a new MCP server that exposes an external API or service in Python or TypeScript.InstallDesign the API client, authenticated tool layer, schemas, pagination, errors, and evaluation cases.Choose TypeScript or Python guidance, then review the service API’s endpoints, authentication requirements, and data models. ↗Mcp IntegrationConnecting or bundling MCP servers in a Claude Code plugin, including authentication and transport configuration.InstallAdd `.mcp.json` or `mcpServers`, configure the chosen transport and authentication, document environment variables, and test tool calls.Create a plugin-root `.mcp.json` or use the `mcpServers` field; supply required environment variables. ↗Mcp Server PatternsA focused Node/TypeScript MCP server using tools, resources, prompts, Zod validation, and local or remote transport.InstallCreate a TypeScript server, define schemas and tool/resource registrations, and select stdio or Streamable HTTP.Install the MCP SDK and Zod; verify current SDK signatures against current MCP documentation before implementation. ↗

Source notes

Inspect evidence and candidate limits 3 candidates

Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.

What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.

Mcp Builder

Source ↗

Use it forBuilding a new MCP server that exposes an external API or service in Python or TypeScript.

Avoid ifYou only need to configure an existing MCP server inside a Claude Code plugin.

ActionInstall

EditsDesign the API client, authenticated tool layer, schemas, pagination, errors, and evaluation cases.

SetupChoose TypeScript or Python guidance, then review the service API’s endpoints, authentication requirements, and data models.

Inspect workflow and compatibility details

ContextHighest-ranked direct match; covers the full server-development workflow.

OutputAn MCP server with well-described, structured tools plus evaluation cases.

ControlComprehensive API coverage with schema-first tools and actionable errors.

InvocationNot yet mapped from the source.

Install scopeNot yet mapped from the source.

Agent fitStrong general-purpose choice for new MCP server work.

Watch outIts TypeScript stack is recommended, but Python is also explicitly supported.

Source-visible capabilitiesMCP server workflowPlans, implements, tests, and evaluates MCP servers for external services.explicit sourceAPI integration infrastructureAPI client authentication, error helpers, response formatting, and pagination.explicit source

CompatibilityTypeScriptdeclarednot runtime-testedPythondeclarednot runtime-tested

Evidence

Directly targets MCP servers that integrate external APIs or services in Python or Node/TypeScript.SKILL.md:lines 1-3 · inspected 2026-07-20 · high confidence

Specifies API authentication, errors, response formatting, and pagination as core infrastructure.SKILL.md:lines 86-93 · inspected 2026-07-20 · high confidence

Provides build and MCP Inspector testing steps.SKILL.md:lines 127-147 · inspected 2026-07-20 · high confidence

Public signal136 /SkillsMP source-specificbest-overallmcp-serverpython-or-typescripttestingexplicit source

Mcp Integration

Source ↗

Use it forConnecting or bundling MCP servers in a Claude Code plugin, including authentication and transport configuration.

Avoid ifYou need a framework-neutral implementation guide for authoring an MCP server from scratch.

ActionInstall

EditsAdd `.mcp.json` or `mcpServers`, configure the chosen transport and authentication, document environment variables, and test tool calls.

SetupCreate a plugin-root `.mcp.json` or use the `mcpServers` field; supply required environment variables.

Inspect workflow and compatibility details

ContextA direct but Claude Code plugin-specific alternative; strongest for integration configuration rather than server internals.

OutputPlugin MCP configuration with documented credentials, allowed tools, and local verification.

ControlExplicit transport, authentication, security, lifecycle, and debugging checklist.

InvocationNot yet mapped from the source.

Install scopeNot yet mapped from the source.

Agent fitBest when the host surface is a Claude Code plugin.

Watch outIts configuration and lifecycle guidance is scoped to Claude Code plugins.

Source-visible capabilitiesMCP configurationConfigures bundled MCP servers through `.mcp.json` or `plugin.json`.explicit sourceTransport and authenticationCovers stdio, SSE, HTTP, and WebSocket with OAuth, token, and environment-variable patterns.explicit source

CompatibilityClaude Code pluginsdeclarednot runtime-tested

Evidence

Directly covers integrating MCP servers into Claude Code plugins to expose external service capabilities as tools.SKILL.md:lines 7-17 · inspected 2026-07-20 · high confidence

Documents `.mcp.json` and inline `mcpServers` configuration methods.SKILL.md:lines 19-64 · inspected 2026-07-20 · high confidence

Includes a local testing and validation checklist for MCP integration.SKILL.md:lines 423-441 · inspected 2026-07-20 · high confidence

Public signal766 /SkillsMP source-specificclaude-code-pluginmcp-configurationauthenticationtransportexplicit source

Mcp Server Patterns

Source ↗

Use it forA focused Node/TypeScript MCP server using tools, resources, prompts, Zod validation, and local or remote transport.

Avoid ifYou need Python guidance, detailed API-client scaffolding, or a full plugin configuration workflow.

ActionInstall

EditsCreate a TypeScript server, define schemas and tool/resource registrations, and select stdio or Streamable HTTP.

SetupInstall the MCP SDK and Zod; verify current SDK signatures against current MCP documentation before implementation.

Inspect workflow and compatibility details

ContextA concise TypeScript-specific substitute with the next-best public-recognition rank among direct MCP-server finalists.

OutputA Node/TypeScript MCP server with validated tools, optional resources/prompts, and transport-separated logic.

ControlSchema-first, transport-independent server design.

InvocationNot yet mapped from the source.

Install scopeNot yet mapped from the source.

Agent fitGood for developers who want a compact TypeScript MCP pattern rather than a broad workflow.

Watch outThe source warns that SDK APIs change and directs users to verify current signatures.

Source-visible capabilitiesMCP primitivesImplements tools, resources, and prompts with current SDK registration patterns.explicit sourceTransport selectionUses stdio for local clients and Streamable HTTP for remote clients.explicit source

CompatibilityNode/TypeScriptdeclarednot runtime-tested

Evidence

Directly applies to new MCP servers, tools/resources, transport selection, SDK upgrades, and registration debugging.SKILL.md:lines 7-13 · inspected 2026-07-20 · high confidence

Defines tools, resources, prompts, and transport choices including Streamable HTTP for remote clients.SKILL.md:lines 17-34 · inspected 2026-07-20 · high confidence

Provides Node/TypeScript SDK and Zod installation/setup guidance.SKILL.md:lines 36-53 · inspected 2026-07-20 · high confidence

Public signal787 /SkillsMP source-specifictypescriptnodeschema-firststreamable-httpexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide ↗

Did this decision map help?