프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Dactic

제작자: Dactic-Monday버전 0.1.2i★ –i클라우드에서 실행
레지스트리 이름io.dactic/dactic-mcp

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: Streamable HTTP
  • 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:

  1. Settings → Connectors 열기
  2. Add custom connector 누르기
  3. 아래 주소를 붙여 넣고 Add 누르기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Add2https://…3
https://mcp.app.dactic.io/mcp

터미널에서 이 명령어를 실행하세요

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

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:

  1. 웹에서 ChatGPT 열기 → Settings → Connectors (Apps)
  2. Create 또는 Add 누르기(일부 요금제는 먼저 Advanced에서 Developer mode를 켜야 해요)
  3. 아래 주소를 붙여 넣고 이름을 정한 뒤 저장하기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Create2https://…3
https://mcp.app.dactic.io/mcp

메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

  • list_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.

  • get_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.

  • load_agent

    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

  • invoke_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 starti

  • resolve_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.

  • check_freshness

    Is my Dactic knowledge up to date? Reports each surface (app sync, knowledge, terminology, 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

  • get_policy

    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.

  • list_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.

  • get_skill

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

  • ask_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 d

  • get_context_bundle

    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 knowledge (confirmed first, then inferred from approved s

  • get_user_context

    Your own Dactic profile for personalising answers: job title, team, department and role; work context (role, guardrails, preferences); knowledge files (paginated, confirmed first; each says confirmed or inferred); connected apps; tools you use. Only ever your own data, even for o

  • get_knowledge_provenance

    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,

  • submit_agent_feedback

    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 w

  • check_against_policy

    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-

  • get_skill_usage

    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 whe

  • synthesize_agent

    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

  • create_agent_from_process

    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). The input includes purpose, concrete ordered steps, trigger, resou

  • get_task_status

    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.

  • search

    Search your Dactic knowledge (your skills, agents and 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.

  • fetch

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

  • get_usage

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

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

  • get_feedback_status

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

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

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

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

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

  • 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 intermediat

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

  • 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: . Returns typed rows, pagination and explicit sync/coverage limits. Older syncs may lack structured columns. Never accepts

  • 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 fr

  • 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 ar

  • 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

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 도메인 dactic.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • ✓ 통과

    엔드포인트 응답

    425ms 만에 응답(HTTP 200)

  • – 해당 없음

    OAuth로 로그인

    로그인 필요 없음

  • ✓ 통과

    도구 설명에 숨겨진 지시 없음

    도구 설명 34개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 32403개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 32403개 중 94%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 32403개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Dactic, 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.2)은 그저께 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, LickityClick

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211어제 업데이트
설치

LickityClick

제작자: lickity.click

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

컴퓨터 또는 클라우드오늘 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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/mcp-server@0.1.0 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:

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

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

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:

npm ci

npm run verify node 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/mcp-server@0.1.0.

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.

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.

PopNx에게 묻기