Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Dactic is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Connect AI clients to your Dactic work context through a hosted MCP service.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http dactic-mcp https://mcp.app.dactic.io/mcp
# 2 — ask your agent for something these tools do
# list_agents, get_agent, load_agent and 31 more
Dactic costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http dactic-mcp https://mcp.app.dactic.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
34 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the Dactic agents you (the signed-in user) have deployed, newest first. Returns each agent's id, name, platform and status. Use load_agent to run one or get_agent for its details. Returns not_found when you have none.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
| limit | integer | no | — |
| cursor | string | no | — |
| enrich | boolean | no | — |
Get one of your Dactic agents by id: its name, platform, status, complete instructions and every skill (name, description, full procedure). Never returns another user's agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| enrich | boolean | no | — |
Load one of your Dactic agents (by agent_id or exact agent_name) so you can run it in this chat: returns its complete instructions and skills. Follow them exactly. Returns not_ready when the agent has no approved instructions, and not_found when no agent matches; it never returns a partial agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | no | — |
| agent_name | string | no | — |
Run one of your deployed Dactic agents. Claude agents start a Managed Agent session; Monday agents are run by Monday's own board automation. The response always includes the agent's complete instructions and skills. Retrying the same request returns the same run instead of starting another.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| input | object | no | — |
| include_context | boolean | no | — |
| idempotency_key | string | no | — |
Look up what company-specific terms mean, from your organization's confirmed Dactic terminology only. Terms that aren't confirmed come back in gaps; never guess their meaning.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| terms | array | yes | — |
| team | string | no | — |
Is my Dactic knowledge up to date? Reports each surface (app sync, confirmed knowledge, terminology, approved playbook, department policies, skills, and optionally one agent) as fresh, stale, empty or unknown, with a recommendation for anything not fresh. Pass refs from other Dactic tools to check specific items. scope=org is for org admins.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | — |
| agent_id | string | no | — |
| refs | array | no | — |
Get your department's current policies with their source document. With query: the policies that apply to it (all of them when your department has few, else the closest matches; coverage says which). Returns not_found when none are published.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| policy_id | string | no | — |
| category | string | no | — |
| query | string | no | — |
| limit | integer | no | — |
List your active Dactic skills (procedures derived from your interviews). disclosure_tier L1 returns a catalog; L2/L3 add the procedure. Use get_skill for one skill. Returns not_found when you have none.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| disclosure_tier | string | no | — |
| limit | integer | no | — |
| query | string | no | — |
| approved_only | boolean | no | — |
Get one of your Dactic skills by id, with its full procedure at disclosure_tier L3.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| skill_id | string | yes | — |
| disclosure_tier | string | no | — |
Answer a question from your own Dactic context: matches holds evidence from your synced work data and current department policies related to the question; your_profile holds your work context, skills, agents and connected apps. When nothing matches, say so; never another user's data, even for org admins.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| limit | integer | no | — |
| source_type | string | no | — |
| board | string | no | Monday board id or board name. Limits evidence to that Monday board and drops other Monday boards plus Chat, Gmail, and any other non-Monday evidence. Only boards the caller has approved are accepted. |
Get everything a task needs from Dactic in one call; use it before doing a task, especially when running an agent. With agent_id: that agent's complete instructions and skills. Without: your most relevant skills. Plus your confirmed knowledge and related evidence, your department's applicable policies with citations, confirmed meanings of company terms (unresolved terms are listed, never guessed)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| agent_id | string | no | — |
| token_budget | integer | no | — |
| include | array | no | — |
Your own Dactic profile for personalising answers: job title, team, department and role; work context (role, guardrails, preferences); confirmed knowledge (paginated; unconfirmed files are counted, not shown); connected apps; tools you use. Only ever your own data, even for org admins.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | — |
| limit | integer | no | — |
| cursor | string | no | — |
Where did that come from? For refs returned by other Dactic tools (1-20), describes each item's source and a confidence of high, medium or low from a fixed rubric, with the rule that applied in basis. Rubric — terminology: high when confirmed with score >= 0.9 and no conflict, medium when confirmed otherwise, low when not confirmed. Knowledge: high when confirmed in an interview, medium when inf
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refs | array | yes | — |
File feedback about one of your own Dactic agents (e.g. 'it keeps CC'ing finance'). Quote the user's words in detail. First call without confirmation_code: you get a preview and a confirmation_code and nothing is saved; show the preview, ask the user to confirm, then call again with the same fields plus confirmation_code. It's applied at the agent's next refresh, not immediately. Only for your own
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent | object | yes | — |
| summary | string | yes | — |
| detail | string | no | — |
| expected_behavior | string | no | — |
| category | string | no | — |
| severity | string | no | — |
| target | object | no | — |
| confirmation_code | string | no | — |
| idempotency_key | string | no | — |
Advisory check of a draft reply, plan or action against your department's Dactic policies. Returns findings that quote the policy and the draft verbatim, with a suggested change, and says how many policies were checked. Present the result as advice: it is never a compliance sign-off. not_assessed means the check couldn't run; the applicable policies are listed instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draft | string | yes | — |
| kind | string | no | — |
| context | string | no | — |
| categories | array | no | — |
How often your Dactic skills were listed and loaded by AI clients (ChatGPT, Claude…) over the last 7, 30 or 90 days, how many live agents use each, and a suggestion (promote, keep, review or trim) with its basis. Suggestions are advice and never change anything. data_since is when counting started; there is no earlier history. scope=org is for org admins.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | — |
| window_days | integer | no | — |
| skill_slug | string | no | — |
| limit | integer | no | — |
| next_cursor | string | no | — |
Draft a new Dactic agent for a task the user describes, built only from the user's own Dactic skills, policies and work context. Runs in the background: it returns a task_id at once; call get_task_status with it until the status is succeeded or failed. The result is a draft saved for review in the Dactic app — it is never deployed from here. If none of the user's skills fit, the result says not_en
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_description | string | yes | — |
| target_platform | string | no | — |
| name | string | no | — |
| idempotency_key | string | no | — |
Draft a new Dactic agent, and the new skills it needs, from a process the user describes in this chat — use this when the user's existing skills don't cover the work (synthesize_agent only reuses existing skills). Before calling, ask the user for the purpose, the concrete steps in order, when it should run, the data sources or tools it uses and anything it must never do; then confirm the summary w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purpose | string | yes | — |
| steps | array | yes | — |
| trigger | string | no | — |
| resources | array | no | — |
| constraints | array | no | — |
| notes | string | no | — |
| name | string | no | — |
| target_platform | string | no | — |
| idempotency_key | string | no | — |
Status of a background task you started (e.g. synthesize_agent): queued, running, succeeded (with its result) or failed (with error_message). Only your own tasks; anything else is not_found.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | — |
Search your Dactic knowledge (your skills, agents and approved playbooks, and your organization's confirmed terminology, plus current department policies). Returns results with an id, title and link; call fetch with an id for the full text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
Fetch the full text of one Dactic item by the id search returned, with a link to it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Your Dactic AI usage (tokens by operation) over the last N days; scope=org is for org admins.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | — |
| days | integer | no | — |
Report recorded sync progress, last successful sync, approved source coverage and safe recovery guidance. Credential linkage is not proof of current access.
No parameter schema on file.
Follow the recorded processing/application state of your submitted agent feedback. No immediate agent change is implied.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feedback_id | string | yes | — |
Match a task to accessible deployed agents by their stored instructions and skills. Returns candidate evidence and limitations; never runs or creates an agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| limit | integer | no | — |
Compare two stored artifact versions of the same accessible agent/platform, with instruction diffs and skill additions/removals. Missing guardrails/parameters remain unknown. Never rolls back or deploys.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| platform | string | no | — |
| from_version | integer | yes | — |
| to_version | integer | yes | — |
Assess task preparation using available knowledge, skills, policies, terminology and sync readiness. Returns blocking/nonblocking gaps; unknown requirements or execution permissions remain unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| agent_id | string | no | — |
| required_inputs | array | no | — |
| available_inputs | array | no | — |
Follow bounded explicit stored links from an approved board, accessible agent/project or confirmed term. Returns entities, relationship bases, citations and missing-link gaps. Text similarity never establishes a dependency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_type | string | yes | — |
| entity_id | string | yes | — |
| limit | integer | no | — |
Retrieve added/updated/removed permitted knowledge and published policies since an actor-bound snapshot cursor. Omit cursor for a complete bounded baseline. Expired cursors or changed scopes/permissions require a fresh baseline. Returns snapshot differences, not every intermediate change event; the host retains the cursor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cursor | string | no | — |
| include | array | no | — |
Find comparable recent runs or resolved feedback owned by you. Returns recorded summaries/outcomes, citations and uncertainty; missing actions/outcomes remain unknown. Past outcomes do not guarantee success.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| situation | string | yes | — |
| limit | integer | no | — |
Query the approved synced Monday item view with supported scalar filters, sorting, grouping and count/sum aggregation. Fields are base identifiers or column:<stored-column-id>. Returns typed rows, pagination and explicit sync/coverage limits. Older syncs may lack structured columns. Never accepts SQL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | string | no | — |
| board_id | string | no | — |
| fields | array | no | — |
| group_by | array | no | — |
| filters | array | no | — |
| sort | array | no | — |
| aggregate | no | — | |
| limit | integer | no | — |
| cursor | string | no | — |
Build advisory human-reviewed workflow options using accessible agents, context gaps, connection/sync readiness and provisional platform capabilities. Separates source, execution-platform and host connectors. Returns next actions and conservative net human-hours estimates only from user-confirmed measurements. Missing measurements trigger a question. Never executes, connects, schedules or deploys.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | yes | — |
| where_stuck | string | no | — |
| agent_id | string | no | — |
| target_platform | string | no | — |
| manual_steps | array | no | — |
| required_inputs | array | no | — |
| available_inputs | array | no | — |
| measurements | object | no | — |
After confirming the user's goal, save a new recommendation iteration containing validated Claude draft proposals from their own skills/context. Optional priorities produce up to three proposals. A proposal never copies an agent or draft the user already has: when their skills are all in use the result is existing_agent_covers with those agents. Returns a background task; poll get_task_status. Mon
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | yes | — |
| priorities | array | no | — |
| target_platform | string | no | — |
| previous_iteration_id | string | no | — |
| idempotency_key | string | no | — |
First deployment of your selected saved draft. Call without confirmation_code for a preview, show it to the user and obtain authorization, then repeat the same definition/target with the code. Checks skills, source approvals and existing deploy readiness/billing gates. Returns a background task; poll get_task_status for deployment state. An existing deployment is identified without redeploying.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| definition_id | string | yes | — |
| target_workspace | string | yes | — |
| confirmation_code | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Dactic or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_agents | no tags | |
| get_agent | no tags | |
| load_agent | no tags | |
| invoke_agent | state-write | state-write: declares readOnlyHint: false |
| resolve_terms | no tags | |
| check_freshness | no tags | |
| get_policy | no tags | |
| list_skills | no tags | |
| get_skill | no tags | |
| ask_knowledge | no tags | |
| get_context_bundle | no tags | |
| get_user_context | no tags | |
| get_knowledge_provenance | no tags | |
| submit_agent_feedback | state-write | state-write: declares readOnlyHint: false |
| check_against_policy | no tags | |
| get_skill_usage | no tags | |
| synthesize_agent | state-write | state-write: declares readOnlyHint: false |
| create_agent_from_process | state-write | state-write: declares readOnlyHint: false |
| get_task_status | no tags | |
| search | no tags | |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| get_usage | no tags | |
| get_sync_status | no tags | |
| get_feedback_status | no tags | |
| recommend_agent | no tags | |
| compare_agent_versions | no tags | |
| find_context_gaps | no tags | |
| get_entity_context | no tags | |
| get_context_delta | no tags | |
| retrieve_similar_cases | no tags | |
| query_work_dataset | no tags | |
| guide_workflow | no tags | |
| recommend_new_agents | state-write | state-write: declares readOnlyHint: false |
| deploy_agent | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Dactic can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.