Nimcp MCP Server

Nimcp MCP server exists for a simple reason — assistants are far more useful when they can act on Nimcp directly instead of describing what you should do. mcpTool: proc echo(text: string): string = ## Echo back the input text return "Echo: " & text.

What you get

• Macro-driven API — - Define servers, tools, resources, and prompts with simple, declarative syntax
• Full MCP 2024-11-05 Support — - Complete implementation of MCP specification with JSON-RPC 2.0
• Multiple Transports — - Supports stdio, SSE, HTTP, and WebSocket transports
• Enhanced Type System — - Support for objects, unions, enums, optional types, and arrays
• Automatic Schema Generation — - JSON schemas generated from Nim type signatures
• Request Context System — - Progress tracking, cancellation, and request lifecycle management

What the assistant can call

Once Nimcp is connected, these are the calls the assistant has available:

• Server — initiated events
• Request — specific state management
• Installation — The Installation tool exposed by this server
• Tools — Tools are functions that LLM applications can call. Define them with the mcpTool macro that plucks out the tool name, description, and JSON schema
• Resources — Resources provide data that can be read by LLM applications:
• Prompts — return @[ McpPromptMessage( role: System, content: createTextContent(&"Review this {language} code for best practices and potential issues.") )

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nimcp's toolset — Server, Request, Installation and 3 more — is a fair guide to whether it matches your workflow. It is maintained by gokr; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the nimcp mcp server does with a few real requests.