mcp-coding
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-codinglist all files in the current directory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-coding
This repository is an experiment to explore the Model Context Protocol (MCP) and local LLM orchestration. It is intended for learning and prototyping, not as a production-ready product.
The project includes:
an MCP HTTP server (
server.ts) with filesystem tools (read_file,write_file,list_files,delete_file)a CLI agent (
main.ts) that talks to the LLM and executes MCP tool calls when needed
Requirements (first-time setup)
If you just cloned this repository, install only:
This repository currently defaults to qwen3.6:latest in adapters/ollama.llm.ts.
If you keep that default, run:
ollama pull qwen3.6:latestRelated MCP server: mcp-cli-catalog
Initialize the project
npm installRun locally
Start MCP server (terminal 1):
npm run serverServer endpoint:
http://localhost:8080/mcp
Start agent (terminal 2):
npm run startIn the interactive prompt, type your requests. To exit:
exitUse MCP Inspector
Make sure the MCP server is running:
npm run serverIn another terminal, start Inspector:
npm run inspectorIn Inspector, connect to:
http://localhost:8080/mcpYou can then inspect available tools and test tool calls against the local MCP server.
Available scripts
npm run build- build TypeScriptnpm test- run Jest testsnpm run start- run the agent (client.ts)npm run start:watch- run the agent in watch modenpm run server- run MCP server (server.ts)npm run server:watch- run MCP server in watch modenpm run inspector- run MCP Inspector
How it works
You enter a prompt in the CLI client.
The agent sends messages to the LLM through Ollama.
If the LLM returns tool calls, the client invokes tools on the MCP server.
Tool results are sent back to the LLM to continue the loop.
Repository structure
.
├── main.ts
├── server.ts
├── adapters/
│ ├── index.ts
│ └── ollama.llm.ts
├── ports/
│ ├── index.ts
│ └── llm.port.ts
├── package.json
└── tsconfig.jsonLicense
ISC
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityCmaintenanceAn MCP server that provides LLMs access to other LLMsLast updated410179MIT
- Alicense-qualityDmaintenanceAn MCP server that publishes CLI tools on your machine for discoverability by LLMsLast updated151MIT
- AlicenseAqualityCmaintenanceMCP Server that enables LLMs to interact with the local filesystem.Last updated1831610MIT
- FlicenseAqualityCmaintenanceAn MCP server that exposes filesystem operations — listing directories, reading, writing, and searching files — as tools an LLM can discover and invoke at runtime.Last updated4
Related MCP Connectors
MCP server for AI dialogue using various LLM models via AceDataCloud
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Local-first RAG engine with MCP server for AI agent integration.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cdemeo92/mcp-coding'
If you have feedback or need assistance with the MCP directory API, please join our Discord server