doings-evidence-mcp

doings-evidence-mcp

This MCP server provides critical evidence assessment for organization-design, leadership and transformation claims, enabling users to critique consulting text, check claims against research, and generate safer phrasing.

Category
访问服务器

README

Doings Evidence MCP

v0.9 Thinking Interface

The default user-facing tool is now think_with_evidence. It helps Doings users think, phrase, challenge and make organizational arguments client-safe. It builds on the evidence engine, but adds:

  • argument mapping,
  • solution-first detection,
  • Doings voice rewriting,
  • client-safe language,
  • evidence-to-language translation,
  • learning nudges that teach better reasoning patterns.

Example:

{
  "input": "We think the client needs a flatter organization to become faster.",
  "context": "Nordic professional-services company, 50-150 employees, project-based client delivery",
  "mode": "thinking_partner"
}

The tool should respond by mapping the reasoning, flagging solution-first risk, asking where speed is actually lost, and producing Doings-voice and client-safe language.

See docs/v0.9-thinking-interface.md.

Local MCP server for critical evidence assessment of organization-design, leadership and transformation claims.

Current version: 0.11.0

v0.11 deployment chain

v0.11 adds a GitHub -> Azure -> remote MCP deployment chain:

  • GitHub Actions workflow for Azure Container Apps
  • Bicep infrastructure template
  • remote MCP smoke test
  • deployment runbook

Start with docs/deploy-chain-runbook.md.

Purpose

Doings Evidence MCP is a critical evidence editor for organizational thinking. It helps Doings distinguish between:

  • academic research
  • internal experience / IP
  • practical heuristics
  • unsupported consulting claims
  • claims that are plausible but overstated
  • text that is usable only with caveats and safer wording

It is not a recommendation generator and it is not a systematic literature review engine.

v0.9 highlights

v0.9 adds a user-facing critique layer on top of the v0.7 evidence engine:

  • intent detection for rough user questions and draft text
  • critique modes: quick_check, rewrite_safely, red_team, evidence_brief
  • critique_org_text tool for day-to-day consulting text
  • can_we_say_this fast check alias
  • consulting-language risk detector
  • safer-phrasing generator
  • narrative response layer that explains what to say, what to avoid and why

Core tools

critique_org_text

Best default tool for human questions, pitch/RFP sentences, rough consulting text and “can we say this?” prompts.

Example:

{
  "input": "Autonomous teams unlock agility and reduce the need for middle management.",
  "context": "Nordic professional-services company, 50-150 employees, project-based client delivery, senior expert dependency.",
  "mode": "auto",
  "includeRawCritique": false
}

Output includes:

  • detected user intent
  • selected critique mode
  • primary claim extracted from the text
  • consulting-language risk
  • narrative answer
  • safer version
  • caveats and warnings

can_we_say_this

Fast practical check for whether a claim or draft sentence is safe enough to say. It uses the same schema as critique_org_text but defaults to practical quick-check behavior.

critique_claim

Research-heavy tool for a specific explicit claim.

Example:

{
  "claim": "Autonomous teams make organizations more agile and reduce the need for middle management.",
  "context": "Nordic professional-services company, 50-150 employees, project-based client delivery, senior expert dependency.",
  "strictness": "high",
  "yearFrom": 2000,
  "maxPapers": 10,
  "fullTextMode": "open_access",
  "maxFullTextPapers": 3,
  "redTeamMode": true
}

Output includes:

  • decomposedClaims
  • levelOfAnalysis
  • levelAlignment
  • contextFit
  • studyTypeProfile
  • evidencePassages
  • redTeam
  • statusLabel: exploratory_evidence_scan_not_systematic_review

search_research_evidence

Searches OpenAlex and Semantic Scholar, optionally escalating to open-access full text.

fetch_doings_document

Fetches one SharePoint/OneDrive document, extracts local text when possible, and can classify, audit and validate high-risk claims.

audit_doings_document_claims

Audits raw text or SharePoint document text for research-checkable claims, nearby citation markers and high-risk unsupported claims.

Use:

{
  "validateHighRiskClaims": true,
  "validationFullTextMode": "open_access",
  "validationRedTeamMode": true
}

rate_evidence_quality

Returns a conservative heuristic rating with study-type profile and full-text coverage.

Critique modes

quick_check

For “kan vi säga detta?” or one rough claim.

Returns a short verdict, why it is risky or usable, safer wording and use-with-caution notes.

rewrite_safely

For pitch/RFP/report wording.

Returns a research-honest rewrite, what changed and what not to imply.

red_team

For finding the weak points.

Returns the most vulnerable assumption, likely skeptical objections, alternative explanations and a stress test.

evidence_brief

For “vad säger forskningen?”

Returns an evidence status, what is better supported, cautions, boundary conditions and safer formulation.

Run locally

npm install
npm run dev

Build:

npm run build
npm start

Environment

Copy .env.example to .env and configure Microsoft Graph if using SharePoint tools.

cp .env.example .env

Minimum SharePoint variables:

MS_TENANT_ID=...
MS_CLIENT_ID=...
MS_GRAPH_SCOPES=Files.Read.All Sites.Read.All offline_access

Research sources

  • OpenAlex for broad scholarly metadata and open-access locations
  • Semantic Scholar for additional academic search and abstracts
  • Open-access PDF/HTML/text fetching when available

Important limitations

This is an exploratory evidence scan, not a systematic literature review. It does not perform formal inclusion/exclusion coding, PRISMA-style review, quality appraisal by multiple reviewers or exhaustive full-text search. Treat outputs as a critical first-pass assessment.

v0.10 remote-ready deployment

v0.10 can run in two modes:

# Local MCP / STDIO
npm run build
npm run start

# Hosted MCP / Streamable HTTP
MCP_REQUIRE_AUTH=true MCP_BEARER_TOKEN=<token> npm run start:http

Hosted endpoints:

GET  /health
POST /mcp
GET  /mcp
DELETE /mcp

See:

docs/remote-mcp-azure.md
docs/github-setup.md
docs/v0.10-remote-ready.md
deployment/example-client-config.local.json
deployment/example-client-config.remote.json

Recommended path:

GitHub repo -> Azure Container Apps -> remote MCP URL -> ChatGPT / MCP-compatible client

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选