Dactic

io.dacticPublished by dactic.ioOfficial publisherv0.1.2Updated Nov 4, 2026

Connect AI clients to your Dactic work context through a hosted MCP service.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryAI & ML

Overview

AI-generated overview

Hosted Dactic MCP server that gives an assistant the signed-in user's own agents, skills, terminology, department policies and work context.

What you can do
  • List, inspect, load and run the user's deployed agents, and draft, recommend, compare or deploy new ones
  • Search and fetch the user's skills, approved playbooks, confirmed terminology and department policies
  • Answer questions from the user's own work context, resolve company terms, and trace where each result came from
  • Check drafts against department policies, file agent feedback, and follow background tasks and sync status
  • Query the approved synced Monday item view and review usage, context gaps, deltas and similar past cases
When to use it
Useful when the assistant should work from a specific organization's own agents, procedures and policies rather than general knowledge, for example running a deployed agent in chat, checking a draft reply against department policy, or drafting and deploying a new agent from existing skills.
Requirements
A remote Streamable HTTP endpoint plus a Dactic account and access to the requested capabilities; available tools depend on account and permissions. Sign-in uses the client's OAuth consent flow. An optional stdio bridge needs Node.js 22.12 or later, and headless or Docker use requires a bearer credential supplied through the DACTIC_MCP_TOKEN environment variable.
Before you install
The server holds work context, policies and synced work data, so treat the OAuth cache directory (MCP_REMOTE_CONFIG_DIR, normally under the user's home) and any DACTIC_MCP_TOKEN value like a password and never commit them. Tools that change data, such as submitting feedback or deploying an agent, ask for confirmation first and return a preview with a confirmation_code; deployment also passes billing gates. Policy checks and recommendations are advisory only, not compliance sign-offs.

Installation

In SourceWeft

  1. Open Dactic in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.dactic%2Fdactic-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dactic": {
      "type": "http",
      "url": "https://mcp.app.dactic.io/mcp"
    }
  }
}

README

Dactic MCP

Connect MCP clients to your Dactic work context through the hosted service at https://mcp.app.dactic.io/mcp. A Dactic account and access to the requested capabilities are required. Available tools depend on your account and permissions.

This repository contains the public client manifests, installation guidance, and complete source for the stdio launcher. The launcher uses the pinned mcp-remote transport and OAuth implementation. Backend processing remains on the hosted Dactic service. Reviewers and users use the same integration.

Draft release: the npm installation example is reserved for after @dactic/[email protected] is published. Use a local checkout today. Marketplace approval and authenticated production verification are tracked in the release checklist.

Connect directly (recommended)

Add a Streamable HTTP MCP server with URL https://mcp.app.dactic.io/mcp in your client's MCP settings, then complete the client's OAuth sign-in and consent flow. No API key is embedded in this repository.

For Cursor, merge the following entry into your existing MCP configuration:

json
{"mcpServers":{"dactic":{"url":"https://mcp.app.dactic.io/mcp"}}}

For Claude Code, use the bundled .mcp.json or run:

sh
claude mcp add --transport http dactic https://mcp.app.dactic.io/mcp

The repository also includes Cursor, Claude, and portable plugin manifests. For a local Claude plugin check, run claude plugin validate .; for a local session, run claude --plugin-dir /absolute/path/to/dactic-v1-mcp-public. See client installation for the marketplace formats.

Connect through stdio

Install Node.js 22.12 or later. From a checkout:

sh
npm cinpm run verifynode src/cli.js --help

Merge examples/stdio.local.json into the host's configuration and replace its absolute path with your checkout path. Launch from the MCP host so stdin/stdout stay connected. The bridge opens your browser when OAuth consent is needed. Do not enter account credentials in client JSON.

After the npm release, examples/stdio.npm.json runs the same bridge using npx -y @dactic/[email protected].

Headless environments and Docker

When your account supports a Dactic bearer credential, supply it through the DACTIC_MCP_TOKEN environment variable. Configure the value in your host's secret settings or a private environment; never commit it. The bridge passes a literal environment placeholder to its child process, never the credential in process arguments. OAuth and bearer credentials retain the backend's normal permission checks.

sh
docker build -t dactic-mcp:local .docker run --rm -i -e DACTIC_MCP_TOKEN dactic-mcp:local

This uses an already-set host environment variable. Do not use -t: stdout must remain a clean MCP stream. Headless Docker requires a bearer credential; an interactive browser OAuth callback is not configured by this container.

Configuration and diagnostics

VariableBehavior
DACTIC_MCP_TOKENOptional bearer credential; omitted means browser OAuth
DACTIC_REQUEST_IDOptional safe correlation ID; otherwise a UUID is created
MCP_REMOTE_CONFIG_DIROptional OAuth cache directory; contains credentials
DACTIC_MCP_URLProduction URL or a loopback fixture for local verification

OAuth requests the base scopes openid offline_access mcp/mcp:tools. Additional capabilities depend on server authorization and client consent; this launcher does not request organization-wide usage scopes by default. OAuth storage and refresh are handled by mcp-remote, normally under ~/.mcp-auth. Protect that cache like a password and do not share it.

The bridge writes only protocol messages to stdout. JSON lifecycle diagnostics go to stderr with a request_id, which is also sent as X-Request-ID to the service. Logs classify connection failures and retain safe stack function frames; upstream response bodies, authorization URLs, and credentials are discarded. Search diagnostics by request_id and events bridge.fail or bridge.dependency.fail. Connection establishment is bounded by a 15-second connect timeout, 60-second headers timeout, 300-second body idle timeout, and 120-second browser authorization callback timeout.

For authentication failures, reconnect using your host's sign-in flow. For permission failures, check account access; repeated authentication will not grant new permissions. For network errors, check endpoint availability and your network. Share only a correlation reference with support.

Public source boundary

Public code implements transport and integration configuration. It contains no retrieval engine, internal prompts, database access, production infrastructure, or customer fixtures. Tool descriptions and schemas returned by the service are visible to MCP clients and may be captured by directory inspection. See review scope, security, and the Dactic privacy policy.

Development

npm run verify checks official schema snapshots, manifest consistency, assets, packaging boundaries, and offline protocol integration tests against a synthetic loopback MCP server. Tests do not contact Dactic or read user credentials. CI runs the same checks and builds the non-root Docker image. No registry or marketplace publication runs in CI.

Source is licensed under MIT. Branding and the hosted service are outside that license; see NOTICE.

Source: README.md at commit 51437d0

Tools

34

list_agents

List my Dactic agents

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.

Parameterslimitcursorenrichtarget

get_agent

Get a Dactic agent

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.

Parametersenrichagent_idrequired

load_agent

Load a Dactic agent to run here

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.

Parametersagent_idagent_name

invoke_agent

Run a Dactic agent

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.

Parametersinputagent_idrequiredidempotency_keyinclude_context

resolve_terms

Look up company terms

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.

Parametersteamtermsrequired

check_freshness

Check if my Dactic knowledge is current

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.

Parametersrefsscopeagent_id

get_policy

Get my department's policies

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.

Parameterslimitquerycategorypolicy_id

list_skills

List my Dactic skills

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.

Parameterslimitqueryapproved_onlydisclosure_tier

get_skill

Get a Dactic skill

Get one of your Dactic skills by id, with its full procedure at disclosure_tier L3.

Parametersskill_idrequireddisclosure_tier

ask_knowledge

Ask my Dactic knowledge

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.

Parametersboardlimitquestionrequiredsource_type

get_context_bundle

Get everything a task needs

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) and a freshness summary. Fits token_budget by dropping whole lower-priority items, listed in omitted.

Parameterstaskrequiredincludeagent_idtoken_budget

get_user_context

My Dactic profile

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.

Parameterslimitcursorsections

get_knowledge_provenance

Where did that come from?

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 inferred from 3+ evidence items (or confirmed without a recorded confirmation), low otherwise or when disputed. Evidence: high when it supports confirmed knowledge, medium when it supports unconfirmed knowledge, low otherwise. Policy: high when in the current published COE version, medium when ingested from a document but not published, low with no source document. Skill: high when the owner has an approved playbook and a live agent uses it, medium when active, low when retired. Playbook: high approved, medium needs follow-up, low otherwise. Never repeats evidence text.

Parametersrefsrequired

submit_agent_feedback

Send feedback about my agent

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 agents.

Parametersagentrequireddetailtargetsummaryrequiredcategoryseverityidempotency_keyconfirmation_codeexpected_behavior

check_against_policy

Check a draft against my policies

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.

Parameterskinddraftrequiredcontextcategories

get_skill_usage

How my Dactic skills are used

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.

Parameterslimitscopeskill_slugnext_cursorwindow_days

synthesize_agent

Draft a new agent from my skills

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_enough_material: then offer create_agent_from_process, which builds the agent and its new skills from the process the user describes. If the user's existing agents or drafts already use every skill that fits, the result says existing_agent_covers and names them instead of drafting a duplicate; for a genuinely new process use create_agent_from_process. Confirm the task with the user before calling. target_platform claude only for now.

Parametersnameidempotency_keytarget_platformtask_descriptionrequired

create_agent_from_process

Create a new agent from a process I describe

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 with them. Runs in the background: returns a task_id; call get_task_status until succeeded (with the draft and its review link) or failed. The draft is saved for review in the Dactic app and is never deployed from here. target_platform claude only; Monday agents are created in the Dactic app.

Parametersnamenotesstepsrequiredpurposerequiredtriggerresourcesconstraintsidempotency_keytarget_platform

get_task_status

Check a Dactic background task

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.

Parameterstask_idrequired

fetch

Fetch a Dactic item

Fetch the full text of one Dactic item by the id search returned, with a link to it.

Parametersidrequired

get_usage

My Dactic AI usage

Your Dactic AI usage (tokens by operation) over the last N days; scope=org is for org admins.

Parametersdaysscope

get_sync_status

Get sync status

Report recorded sync progress, last successful sync, approved source coverage and safe recovery guidance. Credential linkage is not proof of current access.

Takes no parameters.

get_feedback_status

Get feedback status

Follow the recorded processing/application state of your submitted agent feedback. No immediate agent change is implied.

Parametersfeedback_idrequired

recommend_agent

Recommend agent

Match a task to accessible deployed agents by their stored instructions and skills. Returns candidate evidence and limitations; never runs or creates an agent.

Parameterstaskrequiredlimit

compare_agent_versions

Compare agent versions

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.

Parametersagent_idrequiredplatformto_versionrequiredfrom_versionrequired

find_context_gaps

Find context gaps

Assess task preparation using available knowledge, skills, policies, terminology and sync readiness. Returns blocking/nonblocking gaps; unknown requirements or execution permissions remain unknown.

Parameterstaskrequiredagent_idrequired_inputsavailable_inputs

get_entity_context

Get entity context

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.

Parameterslimitentity_idrequiredentity_typerequired

get_context_delta

Get context delta

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.

Parameterscursorinclude

retrieve_similar_cases

Retrieve similar cases

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.

Parameterslimitsituationrequired

query_work_dataset

Query work dataset

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.

Parameterssortviewlimitcursorfieldsfiltersboard_idgroup_byaggregate

guide_workflow

Guide workflow

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.

Parametersgoalrequiredagent_idwhere_stuckmanual_stepsmeasurementsrequired_inputstarget_platformavailable_inputs

recommend_new_agents

Recommend new agents

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. Monday synthesis is unavailable in this path. Never deploys.

Parametersgoalrequiredprioritiesidempotency_keytarget_platformprevious_iteration_id

deploy_agent

Deploy agent

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.

Parametersdefinition_idrequiredtarget_workspacerequiredconfirmation_code

Version history

1
  1. v0.1.2LatestNov 4, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts