Unichat MCP Server
Most developer tooling work still happens through a UI a human drives. Unichat MCP server moves it into the conversation instead. Unichat MCP Server.
Send requests to OpenAI, MistralAI, Anthropic, xAI, Google AI or DeepSeek using MCP protocol via tool or predefined prompts. Vendor API key required.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 4 tools. What each one is for:
unichat — Send a request to unichatTools — The server implements one tool: - unichat: Send a request to unichat - Takes "messages" as required string arguments - Returns a responsePrompts — The Prompts tool exposed by this serverDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPConfiguration is passed through the environment: UNICHAT_MODEL, UNICHAT_API_KEY, YOUR_VENDOR_API_KEY, YOUR_OPENAI_API_KEY. 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.
Plenty of developer tooling 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. Unichat's toolset — unichat, Tools, Prompts and 1 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; 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 |
|---|---|
| unichat | Send a request to unichat |
| Tools | The server implements one tool: - unichat: Send a request to unichat - Takes "messages" as required string arguments - Returns a response |
| Prompts | The Prompts tool exposed by this server. |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script: |
Run published:
```json
{
"mcpServers": {
"unichat-ts-mcp-server": {
"command": "npx",
"args": [
"-y",
"unichat-ts-mcp-server"
],
"env": {
"UNICHAT_MODEL": "YOUR_PREFERRED_MODEL_NAME",
"UNICHAT_API_KEY": "YOUR_VENDOR_API_KEY"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UNICHAT_MODEL | Configuration value read at startup. | Optional |
| UNICHAT_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_VENDOR_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_OPENAI_API_KEY | Credential the server authenticates with. | Yes |
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.