An MCP server for natural language inference
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
uvx omni-nliAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-cogitatortech-omni-nli": {
"url": "https://io-github-cogitatortech-omni-nli.example.com"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
omni-nli is an MCP server for An MCP server for natural language inference. It supports HTTP transport.
Use the generated config in Install. This server runs with uvx omni-nli; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx omni-nli. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx omni-nli. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx omni-nli. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx omni-nli. Add required environment variables before starting Cursor or VS Code.
omni-nli uses HTTP transport. Use the package or command config in Install.
omni-nli inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
omni-nli does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
omni-nlistreamable-http | pypi | 0.1.1 | None advertised |