Enhanciar
Remote MCP server (streamable HTTP) for Enhanciar, the company brain. Ask questions over your team's Slack, Gmail, GitHub, Notion, Jira and Linear and get answers with a citation on every claim; search the generated wiki; run impact analysis on code; and propose Jira, Linear, GitHub, Slack or calendar actions that wait for a person to approve. Endpoint: https://enhanciar.in/enhanciar/mcp/ with an API key (Bearer header). Early access by waitlist.
Hosted MCP Server
npx add-mcp 'https://enhanciar.in/enhanciar/mcp/'Installs into Claude Code, Codex, Cursor and more
Documentation
Early access: API keys are created in the app (Settings → API keys), so you need an account. Join the waitlist if you don’t have one yet.
Endpoint
| Transport | Streamable HTTP (MCP 2025-11-25) |
|---|---|
| URL | https://enhanciar.in/enhanciar/mcp/ |
| Auth | Header Authorization: Bearer dh_<your key> |
| Workspace | Chosen when you create the key. One key = one workspace; add a second server for a second workspace. |
Set-up
Claude Code
claude mcp add --transport http --scope user enhanciar \
https://enhanciar.in/enhanciar/mcp/ \
--header "Authorization: Bearer dh_your_key"
Cursor
Settings → Tools & Integrations → New MCP server → type HTTP, URL https://enhanciar.in/enhanciar/mcp/, header Authorization: Bearer dh_your_key.
Claude Desktop
Claude Desktop’s Connectors UI cannot send a custom header, so bridge it with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"enhanciar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://enhanciar.in/enhanciar/mcp/",
"--header", "Authorization: Bearer dh_your_key"]
}
}
}
Settings → Connections in the app has copy-paste snippets for each client with your key filled in.
Tools
| Tool | What it does |
|---|---|
query | Ask a question in plain language; returns a synthesised answer with a citation on every claim (file:line, Slack permalink, doc paragraph). |
search_wiki | Search the generated wiki. |
get_page / list_pages | Read one wiki page in full; list every page the key can see. |
impact | Blast radius of changing a file, function or module: callers, callees, affected tests and pages, from the graph. |
get_graph | The entity / community graph manifest. |
get_process_map | How a process actually runs across code, people and tools. |
list_repos | Repositories the workspace has ingested. |
list_skills / get_skill | Reusable skills distilled from the codebase. |
propose_action / list_proposed_actions | Draft a Jira, Linear, GitHub, Slack or calendar action into the review queue, and list what is waiting. The server can propose; only a person in the app can approve or execute. |
The review queue is the same Actions queue your team sees in the app, and the pull-request reviews Enhanciar posts come from the same brain, so what an agent proposes, what a person approves and what a reviewer reads all share one source of truth.
What it can never do
- Execute an action. Proposals wait for human approval in the app.
- Reach beyond you. A key is tied to you and one workspace; leave the workspace and the key stops on the next request.
- Bill you for tokens. Model calls run under your own key (BYOK); Enhanciar adds no markup.
Why a remote server and not a plugin
Every MCP client already knows how to talk to a remote server, so there is nothing to install or keep updated per editor. The registry entry, the health checks on Glama and the tool schemas are public, so you can inspect exactly what your agent gets before you connect. Questions: enhanciar@gmail.com.