Give brains to your small models. MCP server enforcing step-by-step Chain-of-Thought.
Cotforce MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Give brains to your small models. MCP server enforcing step-by-step Chain-of-Thought.
A 4-billion-parameter Gemma cannot solve SEND + MORE = MONEY. It's a classic cryptarithmetic puzzle — 8 unique digits, 5 columns, 4 carry values. A bare 4B model guesses randomly. It hallucinates digits. It loses track of carries after column 2.
Once Cotforce MCP is connected, these are the calls the assistant has available:
Example — The Example tool exposed by this serverScripts — The Scripts tool exposed by this serverTesting — The test suite uses Jest with ts-jest (ESM) and @slbdn/mcp-tester for MCP server integration testing:You will need 5 environment variables: MODE, API_BASE_URL, MODEL, MAX_RETRIES, TIMEOUT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
@slbdn/cotforce-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cotforce MCP's toolset — Example, Scripts, Testing — is a fair guide to whether it matches your workflow. It is maintained by islobodan; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Example | The Example tool exposed by this server. |
| Scripts | The Scripts tool exposed by this server. |
| Testing | The test suite uses **Jest** with **ts-jest** (ESM) and **@slbdn/mcp-tester** for MCP server integration testing: |
{
"mcpServers": {
"cotforce": {
"command": "node",
"args": ["node_modules/@slbdn/cotforce-mcp/index.js"],
"env": {
"MODE": "direct",
"API_BASE_URL": "http://localhost:1234/v1",
"MODEL": "gemma-4-e4b-it-mlx"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MODE | Configuration value read at startup. | Optional |
| API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MODEL | Configuration value read at startup. | Optional |
| MAX_RETRIES | Configuration value read at startup. | Optional |
| TIMEOUT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.