Agent MCP Server

If you already use Agent, the agent mcp server is the piece that lets your assistant work with it directly. Encoding-aware, indentation-smart file tools for AI coding agents with SSH, SFTP, and 20+ tools.

What the server does

MCP (Model Context Protocol) tool server for AI coding agents.

• Tab indentation breaks — LLMs output spaces, but your project uses tabs. The built-in Edit tool writes spaces as-is, corrupting your indentation style
• Encoding corruption — Editing EUC-KR, Shift-JIS, or GB18030 files silently converts them to UTF-8, breaking legacy projects
• Too many separate tools — Making the agent find, install, and configure Redis CLI, MySQL client, SSH client, etc. is tedious and error-prone. agent-tool bundles 50 tools into a single binary -- one install, everything works
• Network censorship — In some countries, government-level web filtering breaks plain curl/wget requests. agent-tool uses ECH (Encrypted Client Hello) and DoH (DNS over HTTPS) by default to work around these restrictions

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Options — The Options tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: AGENT_TOOL_FALLBACK_ENCODING, BRAVE_SEARCH_API_KEY, NAVER_CLIENT_ID, NAVER_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

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

Where it fits

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Agent's toolset — Options — is a fair guide to whether it matches your workflow. It is maintained by knewstimek; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• 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.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.