MCP-Server
Enhanciar — company brain
in.enhanciar/enhanciar
Was dieses MCP kann
Searches a company's ingested code, Slack and documentation, provides cited answers and dependency impact analysis, and proposes actions for human approval.
Funktionen
Tools
12
Tools
get_graph
Return the community/knowledge graph manifest for visualisation.
Useful when the calling agent wants the high-level structure of the
key's workspace (clusters, hub nodes, cross-references) rather than
the contents of any one page. Returns ``{nodes, edges, communities,
stats}`` â exact shape mirrors the ``/api/wiki/graph`` REST endpoint.
Eingabeschema
{'type': 'object', 'title': 'get_graphArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', 'title': 'get_graphDictOutput', 'additionalProperties': True}
get_page
Fetch a single wiki page from the key's workspace.
Args:
category: One of ``entities | concepts | people | decisions |
sources | flows | infrastructure | tickets``.
name: Page slug (without ``.md`` extension), as returned by
``list_pages`` / ``search_wiki``.
Returns ``{category, name, content}`` â ``content`` is the full
markdown body including YAML frontmatter. Returns ``{error: "..."}``
if the page doesn't exist.
Eingabeschema
{'type': 'object', 'title': 'get_pageArguments', 'properties': {'name': {'title': 'Name', 'default': ''}, 'page': {'title': 'Page', 'default': ''}, 'path': {'title': 'Path', 'default': ''}, 'slug': {'title': 'Slug', 'default': ''}, 'title': {'title': 'Title', 'default': ''}, 'category': {'title': 'Category', 'default': ''}}}
Ausgabeschema
{'type': 'object', 'title': 'get_pageDictOutput', 'additionalProperties': True}
get_process_map
Return the "living map of how the company works" for the key's workspace.
A graph of process nodes (compiled skills), the external systems
they touch (GitHub, Slack, Jira, â¦), the wiki docs they were
derived from, and team groups â with derived_from / uses /
references edges. Use this when the agent wants the high-level
operational structure rather than one skill's steps.
Eingabeschema
{'type': 'object', 'title': 'get_process_mapArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', 'title': 'get_process_mapDictOutput', 'additionalProperties': True}
get_skill
Fetch one compiled skill by name (slug from ``list_skills``).
Returns ``{name, markdown, meta}`` â ``markdown`` is the full
agent-executable SKILL.md content (frontmatter + steps), ``meta``
is the parsed frontmatter. Includes an ``error`` key when the
skill doesn't exist (with the available names).
Eingabeschema
{'type': 'object', 'title': 'get_skillArguments', 'required': ['name'], 'properties': {'name': {'type': 'string', 'title': 'Name'}}}
Ausgabeschema
{'type': 'object', 'title': 'get_skillDictOutput', 'additionalProperties': True}
impact
Compute the blast radius of changing ``target`` in the key's workspace.
Use this before editing code to see what a change ripples into:
direct callers/callees, every affected file, the affected tests, the
transitive dependency set, and example dependency paths with per-path
facts (hops, dependents at the endpoint, whether it lands in a test).
There is deliberately no risk score. There was one â thresholds on the
transitive count â and it was a verdict the caller could not check or
argue with. The counts it was computed from are all here; judge from
those.
Args:
target: A graph node id, wiki page name, file path
(``micrograd/engine.py``), or a function fqn (``engine.py::func``).
depth: How many hops to traverse the call graph (default 2).
Returns the impact dict â ``{target, label, found, direct_callers,
direct_callees, affected_files, affected_tests, transitive_nodes,
transitive_count, paths, path_facts}``.
Eingabeschema
{'type': 'object', 'title': 'impactArguments', 'required': ['target'], 'properties': {'depth': {'type': 'integer', 'title': 'Depth', 'default': 2}, 'target': {'type': 'string', 'title': 'Target'}}}
Ausgabeschema
{'type': 'object', 'title': 'impactDictOutput', 'additionalProperties': True}
list_pages
List every wiki page the caller can see in the key's workspace.
Returns a list of ``{category, name, title}`` records â feed each
one to ``get_page`` to fetch the full markdown body. Use this first
when you want a directory view; for a specific question prefer
``query`` which handles retrieval for you.
Eingabeschema
{'type': 'object', 'title': 'list_pagesArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', 'title': 'list_pagesOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}, 'title': 'Result'}}}
list_proposed_actions
List the key's workspace's proposed actions (the approval queue).
Read-only. Optionally filter by ``status`` (proposed / approved /
executing / done / failed / dismissed). Returns ``{id, action_type,
status, source, title, source_doc_id, external_id}`` per proposal.
NOTE: MCP can read and PROPOSE actions but deliberately cannot approve
or execute them â a human approves every action in the app UI.
Eingabeschema
{'type': 'object', 'title': 'list_proposed_actionsArguments', 'properties': {'status': {'type': 'string', 'title': 'Status', 'default': ''}}}
Ausgabeschema
{'type': 'object', 'title': 'list_proposed_actionsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_repos
List the repos ingested into the key's workspace.
Returns ``{full_name, branch, last_ingested_at}`` records. Use this when
the agent needs to know what context is available before asking a
question.
Reads what ingest actually recorded for this namespace: ``repos.json``
(the repoâclone map every other read path resolves through) plus the
per-repo ``_state`` files that carry the branch and the last run's
timestamp.
It used to read a Firestore subcollection ``users/{uid}/repos``, which
was wrong twice over. It was keyed by the person rather than the
workspace â the bug this module was fixed for â and nothing in the
codebase has ever written to that path, so the tool returned an empty
list to everyone, forever. Hence ``branch`` rather than the old
``default_branch``: the state file records the branch that was actually
ingested, and no caller can be depending on a key that never had a row
under it.
Eingabeschema
{'type': 'object', 'title': 'list_reposArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', 'title': 'list_reposOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_skills
List the compiled skills (recurring procedures) in the key's workspace.
Skills are agent-executable SKILL.md pages mined from that workspace's
wiki by the skills compiler. Returns ``{name, title, description,
confidence, last_compiled, sources}`` records â feed a ``name`` to
``get_skill`` for the full markdown. Empty list = nothing compiled
yet (the user can run a compile from Enhanciar's UI or API).
Eingabeschema
{'type': 'object', 'title': 'list_skillsArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', 'title': 'list_skillsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
propose_action
Propose a new action for human approval (does NOT execute it).
``action_type`` is a registered executor id (e.g. ``jira.create_issue``,
``linear.create_issue``, ``github.create_issue``). The proposal lands in
the key's workspace's approval queue where a person picks the target and
approves it â approve/execute are intentionally NOT exposed over MCP.
Returns the created ``{id, action_type, status}`` or an ``error``.
Eingabeschema
{'type': 'object', 'title': 'propose_actionArguments', 'required': ['action_type', 'title'], 'properties': {'title': {'type': 'string', 'title': 'Title'}, 'evidence': {'type': 'string', 'title': 'Evidence', 'default': ''}, 'action_type': {'type': 'string', 'title': 'Action Type'}, 'description': {'type': 'string', 'title': 'Description', 'default': ''}}}
Ausgabeschema
{'type': 'object', 'title': 'propose_actionDictOutput', 'additionalProperties': True}
query
Ask Enhanciar a natural-language question grounded in the key's workspace.
This is the high-level tool â use it for any "what does X do",
"why did we choose Y", "where is Z handled" question. It runs
the full retrieval + synthesis pipeline and returns the answer
plus citations.
Args:
question: Natural-language question.
model: Optional model id override (``gemini-2.5-flash``,
``gpt-4o``, ``claude-sonnet-4-5``, etc.). If omitted the
saved default is used â the workspace's in a team workspace,
the caller's own in a personal one.
Returns ``{answer, sources, model}`` â ``sources`` is a list of
``{category, name, url}`` citations the LLM grounded its answer
in. Surface them to the human so they can verify. When the workspace
has nothing ingested at all you get ``{answer, empty_brain: true}``
and no sources: that is a statement about the workspace, not a failed
search, so rephrasing the question will not change it.
Eingabeschema
{'type': 'object', 'title': 'queryArguments', 'required': ['question'], 'properties': {'model': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Model', 'default': None}, 'question': {'type': 'string', 'title': 'Question'}}}
Ausgabeschema
{'type': 'object', 'title': 'queryDictOutput', 'additionalProperties': True}
search_wiki
Substring search across the wiki pages in the key's workspace.
Cheap and deterministic â no embedding required. Returns up to
``limit`` (default 20, max 50) ``{category, name, title, snippet}``
hits. The ``snippet`` is a short window around the first match,
safe to surface in chat as a citation preview.
For semantic / natural-language questions prefer ``query``.
Eingabeschema
{'type': 'object', 'title': 'search_wikiArguments', 'required': ['query'], 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 20}, 'query': {'type': 'string', 'title': 'Query'}}}
Ausgabeschema
{'type': 'object', 'title': 'search_wikiOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
Verlauf
Letzte Tool-Änderungen
Geändert
get_page
1. October 2026 02:43
Hinzugefügt
propose_action
21. September 2026 02:40
Hinzugefügt
list_proposed_actions
21. September 2026 02:40
Hinzugefügt
get_process_map
21. September 2026 02:40
Hinzugefügt
get_skill
21. September 2026 02:40
Hinzugefügt
list_skills
21. September 2026 02:40
Hinzugefügt
list_repos
21. September 2026 02:40
Hinzugefügt
get_graph
21. September 2026 02:40
Hinzugefügt
impact
21. September 2026 02:40
Hinzugefügt
query
21. September 2026 02:40
Hinzugefügt
get_page
21. September 2026 02:40
Hinzugefügt
search_wiki
21. September 2026 02:40
Hinzugefügt
list_pages
21. September 2026 02:40
Entdecken
Ähnliche MCP-Server
ALM X++ MCP Server
io.github.alimbenhelal-pro/alm-xpp-mcp
Supports D365 Finance and Operations development with X++ and AOT search, code analysis, Azure DevOps workflows, telemetry querie…
GQLTeam (Dan Podina)
com.gqlteam/site
Exposes a software architect's consulting services, case studies, articles, ventures, profile, and contact or booking details.
Stable Baseline
io.stablebaseline/sb
Manages company documents, knowledge graphs, whiteboards, projects, plans, tasks, teams, and improvement workflows.
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
cypher-mcp
io.github.lonniev/cypher-mcp
Provides named Cypher graph queries and code-orientation tools for tracing capabilities, symbols, invariants, provenance, changes…
mcp
io.nestr/mcp
Manages Nestr workspaces, roles, circles, tensions, governance proposals, comments, daily plans, graph relationships, agents, and…
canton-ccpedia
io.github.UnityNodes/canton-ccpedia
Searches and explains Canton Network and Daml documentation, governance proposals, forums, code examples, APIs, releases, and eco…
Kaiku
tech.kaiku/kaiku
Manages team issues, comments, attachments, projects, wiki pages, and related development workflows.