@tacitai/mcp-server 0.6.25 → 0.6.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/prompts.d.ts CHANGED
@@ -118,8 +118,8 @@ export declare const EXPERIENCES: readonly [{
118
118
  readonly name: "Research & Publish";
119
119
  readonly tier: 2;
120
120
  readonly tierName: "The Operating System";
121
- readonly action: "Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Search workspace knowledge via tacit_search or tacit_synthesize. (2) Search the web for current information. (3) Combine findings into a STYLED HTML REPORT — this MUST be a proper designed artifact opened in the browser for the user to see, not plain text in the chat. The report should have a title, date, executive summary, sections with findings, citations, and a professional layout. Use the artifact/design tools available to create and open the HTML report so the user sees it in their browser. (4) After the report is created, route it through the GM workflow (tacit_gm_ingest) so the GM proposes where to file it. The user approves placement. The key deliverable is the HTML report opened in the browser — the user should SEE a polished document, not just read text in the terminal.";
122
- readonly signal: "First research artifact published as an HTML report opened in the browser, then filed via GM workflow";
121
+ readonly action: "Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Search workspace knowledge via tacit_search or tacit_synthesize. (2) Search the web for current information. (3) Combine findings into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.";
122
+ readonly signal: "First research artifact published as a Claude artifact in the browser, then the HTML file ingested and placed via GM workflow";
123
123
  readonly tip: "After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.";
124
124
  }, {
125
125
  readonly id: "run_sales";
@@ -127,7 +127,7 @@ export declare const EXPERIENCES: readonly [{
127
127
  readonly name: "Run Sales";
128
128
  readonly tier: 2;
129
129
  readonly tierName: "The Operating System";
130
- readonly action: "Part 1 — Discovery Brief: Say \"Prepare a discovery brief for a potential client.\" TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT opened in the browser (same as Experience 7). Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY: (1) Call tacit_voice_list_profiles to find the user's voice profile. A profile MUST exist — voice samples were pre-loaded during workspace setup. (2) Call tacit_compose_in_voice with the email request and the user's profile. This uses TACIT's actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user's voice — that is fake voice matching. NEVER offer to \"paste a sample email\" or \"upload writing samples\" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say \"I expected to find your voice profile but it is not set up yet — let me check with the team\" and move on. Do NOT fall back to LLM-generated voice mimicry.";
130
+ readonly action: "Part 1 — Discovery Brief: Say \"Prepare a discovery brief for a potential client.\" TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY: (1) Call tacit_voice_list_profiles to find the user's voice profile. A profile MUST exist — voice samples were pre-loaded during workspace setup. (2) Call tacit_compose_in_voice with the email request and the user's profile. This uses TACIT's actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user's voice — that is fake voice matching. NEVER offer to \"paste a sample email\" or \"upload writing samples\" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say \"I expected to find your voice profile but it is not set up yet — let me check with the team\" and move on. Do NOT fall back to LLM-generated voice mimicry.";
131
131
  readonly signal: "First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)";
132
132
  readonly tip: "Voice Resonance is a real system — it analyzes your writing samples to capture your cadence, vocabulary, and patterns. Every \"in my voice\" request routes through this system.";
133
133
  }, {
@@ -145,8 +145,8 @@ export declare const EXPERIENCES: readonly [{
145
145
  readonly name: "Audit Your Business";
146
146
  readonly tier: 2;
147
147
  readonly tierName: "The Operating System";
148
- readonly action: "Ask \"How healthy is our business?\" or request a pulse audit.";
149
- readonly signal: "First scored business health audit";
148
+ readonly action: "Run a business health audit. Ask the user \"How healthy is our business?\" or suggest a pulse audit across their workspace. Then: (1) Gather data — call tacit_pyramid_list_portfolios, tacit_pyramid_list_programs, tacit_pyramid_list_value_streams to assess structure completeness. Call tacit_kb_freshness to check knowledge currency. Call tacit_lake_browse_catalog to gauge content volume. Check connector status from the MCP tool list. (2) Score each dimension (structure, knowledge freshness, content depth, tool connectivity, voice readiness) and produce a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk. The report should include dimension scores, a summary health grade, and concrete next steps. (3) After the artifact is saved, ingest the HTML file via tacit_gm_ingest for placement. The user approves where it goes.";
149
+ readonly signal: "First scored business health audit published as a Claude artifact, then filed via GM workflow";
150
150
  readonly tip: "You can also say \"Have COO review our operational health\" — COO coordinates cross-team status and health checks.";
151
151
  }, {
152
152
  readonly id: "operating_rhythm";
package/dist/prompts.js CHANGED
@@ -197,10 +197,10 @@ export const EXPERIENCES = [
197
197
  { id: 'feed_it', num: 4, name: 'Feed It', tier: 1, tierName: 'Orient & Equip', action: 'Turn your first answer into a workspace document. Say: "Take what you just told me and add it to the workspace." TACIT will use the synthesis from your last question as the document body and route it through your General Manager. The GM will classify it, then propose where it should live in your workspace. You approve before anything moves. If you already know where you want it, say so — otherwise say "you decide" and the GM will recommend a spot.', signal: 'First content ingested and placed via GM propose-then-approve', tip: 'Your General Manager handles content routing and placement. Everything goes through a propose-then-approve flow — the GM recommends where content belongs, and nothing moves without your say-so.' },
198
198
  { id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: 'Show the user their current Pyramid structure by calling tacit_pyramid_list_portfolios, then tacit_pyramid_list_programs for each portfolio. Present a clear map of what exists. Then invite the user to make ONE change to prove they can reshape it — suggest something concrete like: "Want to create a new program, rename something, or move content around? Pick one and I will walk you through it." WAIT for the user to try something. Do NOT mark this experience complete until the user has either (a) made a structural change (create, rename, move) or (b) explicitly said they are satisfied with the current structure and want to move on. Showing the map alone is not completion — the user must interact with the structure.', signal: 'User has explored their workspace map AND either made a change or confirmed they are satisfied with the current structure', tip: 'You can always reorganize later. Say "Move this to [collection]" or "Create a new program for [topic]" anytime. Your General Manager proposes, you approve.' },
199
199
  { id: 'connect_your_tools', num: 6, name: 'Connect Your Tools', tier: 1, tierName: 'Orient & Equip', action: 'First, CHECK what is already connected before telling the user anything: (1) Call tacit_github_list_connections to see GitHub repo connections. (2) Check your available MCP tool list — if you have Gmail tools (mcp__claude_ai_Gmail__*), Gmail IS connected. If you have Slack tools (mcp__plugin_*_slack__*), Slack IS connected. If you have Google Calendar tools, Calendar IS connected. If you have Google Drive tools, Drive IS connected. Present a CONNECTION STATUS showing what is already active and what is not. For anything already connected, say "Already connected — ready to use." For anything not connected, explain how to connect it via claude.ai Settings → Integrations. Also show GitHub workspace connections from step 1. Do NOT say a tool is disconnected if you can see its MCP tools in your available tool list. WAIT for the user to either connect something new or confirm they want to move on.', signal: 'User knows their connection status and has either connected new tools or confirmed they are ready to proceed', tip: 'GitHub connections sync your repos into the workspace. Gmail and Slack power the Morning Brief. Google Drive lets you pull in documents directly.' },
200
- { id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Search workspace knowledge via tacit_search or tacit_synthesize. (2) Search the web for current information. (3) Combine findings into a STYLED HTML REPORT — this MUST be a proper designed artifact opened in the browser for the user to see, not plain text in the chat. The report should have a title, date, executive summary, sections with findings, citations, and a professional layout. Use the artifact/design tools available to create and open the HTML report so the user sees it in their browser. (4) After the report is created, route it through the GM workflow (tacit_gm_ingest) so the GM proposes where to file it. The user approves placement. The key deliverable is the HTML report opened in the browser — the user should SEE a polished document, not just read text in the terminal.', signal: 'First research artifact published as an HTML report opened in the browser, then filed via GM workflow', tip: 'After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.' },
201
- { id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: 'Part 1 — Discovery Brief: Say "Prepare a discovery brief for a potential client." TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT opened in the browser (same as Experience 7). Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY: (1) Call tacit_voice_list_profiles to find the user\'s voice profile. A profile MUST exist — voice samples were pre-loaded during workspace setup. (2) Call tacit_compose_in_voice with the email request and the user\'s profile. This uses TACIT\'s actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user\'s voice — that is fake voice matching. NEVER offer to "paste a sample email" or "upload writing samples" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say "I expected to find your voice profile but it is not set up yet — let me check with the team" and move on. Do NOT fall back to LLM-generated voice mimicry.', signal: 'First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)', tip: 'Voice Resonance is a real system — it analyzes your writing samples to capture your cadence, vocabulary, and patterns. Every "in my voice" request routes through this system.' },
200
+ { id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Search workspace knowledge via tacit_search or tacit_synthesize. (2) Search the web for current information. (3) Combine findings into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.', signal: 'First research artifact published as a Claude artifact in the browser, then the HTML file ingested and placed via GM workflow', tip: 'After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.' },
201
+ { id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: 'Part 1 — Discovery Brief: Say "Prepare a discovery brief for a potential client." TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY: (1) Call tacit_voice_list_profiles to find the user\'s voice profile. A profile MUST exist — voice samples were pre-loaded during workspace setup. (2) Call tacit_compose_in_voice with the email request and the user\'s profile. This uses TACIT\'s actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user\'s voice — that is fake voice matching. NEVER offer to "paste a sample email" or "upload writing samples" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say "I expected to find your voice profile but it is not set up yet — let me check with the team" and move on. Do NOT fall back to LLM-generated voice mimicry.', signal: 'First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)', tip: 'Voice Resonance is a real system — it analyzes your writing samples to capture your cadence, vocabulary, and patterns. Every "in my voice" request routes through this system.' },
202
202
  { id: 'morning_brief', num: 9, name: 'Morning Brief', tier: 2, tierName: 'The Operating System', action: 'IMPORTANT — CONNECTOR DETECTION: Before running the brief, CHECK your available MCP tool list to determine what is connected. Gmail IS connected if you have mcp__claude_ai_Gmail__* tools available. Slack IS connected if you have mcp__plugin_*_slack__* tools. Calendar IS connected if you have mcp__claude_ai_Google_Calendar__* tools. Do NOT say "Gmail not connected" if you can see Gmail MCP tools — that is a false negative. Run the COS daily brief: gather workspace state (programs, deadlines, proposals, KB freshness), and for each connected tool, pull real data — Gmail threads, Slack channels, Calendar events. Present the full operating picture. If a connector genuinely has no MCP tools available, say "not yet connected" and explain how to connect via claude.ai Integrations. After the brief, offer to draft a team message using tacit_compose_in_voice (same voice system as Experience 8 — NEVER LLM approximation).', signal: 'First daily operating picture with accurate connector status and real data from connected tools', tip: 'Meet your executive team. COS (Chief of Staff — daily ops, email, meetings), COO (Chief Operating Officer — business ops, sales, audits), GM (General Manager — content ingestion, classification, pyramid placement). Address them by name to route through their workflow.' },
203
- { id: 'audit_business', num: 10, name: 'Audit Your Business', tier: 2, tierName: 'The Operating System', action: 'Ask "How healthy is our business?" or request a pulse audit.', signal: 'First scored business health audit', tip: 'You can also say "Have COO review our operational health" — COO coordinates cross-team status and health checks.' },
203
+ { id: 'audit_business', num: 10, name: 'Audit Your Business', tier: 2, tierName: 'The Operating System', action: 'Run a business health audit. Ask the user "How healthy is our business?" or suggest a pulse audit across their workspace. Then: (1) Gather data — call tacit_pyramid_list_portfolios, tacit_pyramid_list_programs, tacit_pyramid_list_value_streams to assess structure completeness. Call tacit_kb_freshness to check knowledge currency. Call tacit_lake_browse_catalog to gauge content volume. Check connector status from the MCP tool list. (2) Score each dimension (structure, knowledge freshness, content depth, tool connectivity, voice readiness) and produce a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk. The report should include dimension scores, a summary health grade, and concrete next steps. (3) After the artifact is saved, ingest the HTML file via tacit_gm_ingest for placement. The user approves where it goes.', signal: 'First scored business health audit published as a Claude artifact, then filed via GM workflow', tip: 'You can also say "Have COO review our operational health" — COO coordinates cross-team status and health checks.' },
204
204
  { id: 'operating_rhythm', num: 11, name: 'Your Operating Rhythm', tier: 3, tierName: 'Agentic Mastery', action: 'Summarize what the user has accomplished across the onboarding and suggest their operating rhythm. CONNECTOR STATUS: Check your available MCP tool list — if you have Gmail/Slack/Calendar/Drive MCP tools, those ARE connected. Do NOT say they are disconnected. VOICE: Call tacit_voice_list_profiles — if profiles exist, voice is ready. Do NOT ask the user to upload samples if profiles already exist. Focus on: (1) Daily rhythm — morning brief via COS, email triage, meeting prep. (2) Weekly rhythm — COO business review, GM content organization. (3) Delegation — crew dispatch for complex deliverables. (4) What to explore next based on what they have connected and used.', signal: 'User has a clear picture of their operating rhythm and next steps', tip: 'By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.' },
205
205
  ];
206
206
  export function registerPrompts(server, getClientFn) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tacitai/mcp-server",
3
- "version": "0.6.25",
3
+ "version": "0.6.26",
4
4
  "description": "stdio MCP server wrapping Tacit /api/v1 REST/SSE API",
5
5
  "license": "UNLICENSED",
6
6
  "repository": {