@tacitai/mcp-server 0.6.24 → 0.6.25
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 +16 -16
- package/dist/prompts.js +25 -6
- package/package.json +2 -5
package/dist/prompts.d.ts
CHANGED
|
@@ -100,26 +100,26 @@ export declare const EXPERIENCES: readonly [{
|
|
|
100
100
|
readonly name: "Build Your Map";
|
|
101
101
|
readonly tier: 1;
|
|
102
102
|
readonly tierName: "Orient & Equip";
|
|
103
|
-
readonly action: "
|
|
104
|
-
readonly signal: "
|
|
105
|
-
readonly tip: "You can always reorganize later. Say \"Move this to [collection]\" or \"Create a new
|
|
103
|
+
readonly 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.";
|
|
104
|
+
readonly signal: "User has explored their workspace map AND either made a change or confirmed they are satisfied with the current structure";
|
|
105
|
+
readonly 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.";
|
|
106
106
|
}, {
|
|
107
107
|
readonly id: "connect_your_tools";
|
|
108
108
|
readonly num: 6;
|
|
109
109
|
readonly name: "Connect Your Tools";
|
|
110
110
|
readonly tier: 1;
|
|
111
111
|
readonly tierName: "Orient & Equip";
|
|
112
|
-
readonly action: "
|
|
113
|
-
readonly signal: "
|
|
114
|
-
readonly tip: "";
|
|
112
|
+
readonly 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.";
|
|
113
|
+
readonly signal: "User knows their connection status and has either connected new tools or confirmed they are ready to proceed";
|
|
114
|
+
readonly tip: "GitHub connections sync your repos into the workspace. Gmail and Slack power the Morning Brief. Google Drive lets you pull in documents directly.";
|
|
115
115
|
}, {
|
|
116
116
|
readonly id: "research_publish";
|
|
117
117
|
readonly num: 7;
|
|
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
|
|
122
|
-
readonly signal: "First research artifact published
|
|
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";
|
|
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,18 +127,18 @@ 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: "
|
|
131
|
-
readonly signal: "First sales deliverable
|
|
132
|
-
readonly tip: "Voice
|
|
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.";
|
|
131
|
+
readonly signal: "First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)";
|
|
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
|
}, {
|
|
134
134
|
readonly id: "morning_brief";
|
|
135
135
|
readonly num: 9;
|
|
136
136
|
readonly name: "Morning Brief";
|
|
137
137
|
readonly tier: 2;
|
|
138
138
|
readonly tierName: "The Operating System";
|
|
139
|
-
readonly action: "
|
|
140
|
-
readonly signal: "First daily operating picture with
|
|
141
|
-
readonly tip: "Meet your executive team.
|
|
139
|
+
readonly 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).";
|
|
140
|
+
readonly signal: "First daily operating picture with accurate connector status and real data from connected tools";
|
|
141
|
+
readonly 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.";
|
|
142
142
|
}, {
|
|
143
143
|
readonly id: "audit_business";
|
|
144
144
|
readonly num: 10;
|
|
@@ -154,8 +154,8 @@ export declare const EXPERIENCES: readonly [{
|
|
|
154
154
|
readonly name: "Your Operating Rhythm";
|
|
155
155
|
readonly tier: 3;
|
|
156
156
|
readonly tierName: "Agentic Mastery";
|
|
157
|
-
readonly action: "
|
|
158
|
-
readonly signal: "
|
|
157
|
+
readonly 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.";
|
|
158
|
+
readonly signal: "User has a clear picture of their operating rhythm and next steps";
|
|
159
159
|
readonly tip: "By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.";
|
|
160
160
|
}];
|
|
161
161
|
export declare function registerPrompts(server: McpServer, getClientFn?: () => Promise<TacitClient>): void;
|
package/dist/prompts.js
CHANGED
|
@@ -18,6 +18,25 @@ function buildAssistantSystemPrompt(state) {
|
|
|
18
18
|
lines.push('- Never narrate internal routing decisions, retrieval path choices, or fallback strategies. If one approach does not return results, silently try another. The user should see the answer, not the search process.');
|
|
19
19
|
lines.push('- When a capability is unavailable (missing API key, unconnected service, feature not configured), be kind and reassuring. Say what you CAN do, not what is broken. For example: "Deep research works best with a Gemini API key — I do not see one set up yet, but that is no problem. I have great research tools built in, so let me use those today." Never announce a limitation bluntly or make the user feel their setup is wrong.');
|
|
20
20
|
lines.push('');
|
|
21
|
+
lines.push('## Connector detection (MANDATORY)');
|
|
22
|
+
lines.push('');
|
|
23
|
+
lines.push('NEVER assume a tool is disconnected without checking. Your MCP tool list IS the source of truth:');
|
|
24
|
+
lines.push('- Gmail IS connected if you have tools matching mcp__claude_ai_Gmail__*');
|
|
25
|
+
lines.push('- Slack IS connected if you have tools matching mcp__plugin_*_slack__*');
|
|
26
|
+
lines.push('- Google Calendar IS connected if you have tools matching mcp__claude_ai_Google_Calendar__*');
|
|
27
|
+
lines.push('- Google Drive IS connected if you have tools matching mcp__claude_ai_Google_Drive__*');
|
|
28
|
+
lines.push('- GitHub connections: call tacit_github_list_connections to check workspace repo connections');
|
|
29
|
+
lines.push('If a tool is in your available tool list, it IS connected. Do NOT tell the user to "connect" something that is already connected. When presenting connector status, check your tool list first.');
|
|
30
|
+
lines.push('');
|
|
31
|
+
lines.push('## Voice composition (MANDATORY)');
|
|
32
|
+
lines.push('');
|
|
33
|
+
lines.push('When the user asks for anything "in my voice" or you need voice-matched composition:');
|
|
34
|
+
lines.push('1. Call tacit_voice_list_profiles to find their voice profile.');
|
|
35
|
+
lines.push('2. Call tacit_compose_in_voice with the request. This uses TACIT Voice Resonance — a real system that analyzes writing samples to capture cadence, vocabulary, and patterns.');
|
|
36
|
+
lines.push('3. NEVER draft text yourself and claim it matches the user\'s voice. That is LLM approximation, not voice matching.');
|
|
37
|
+
lines.push('4. NEVER offer to "paste a sample email" or "upload writing samples" during onboarding — voice profiles are pre-loaded during workspace setup.');
|
|
38
|
+
lines.push('5. If no voice profile exists, say so honestly and move on — do not fake it.');
|
|
39
|
+
lines.push('');
|
|
21
40
|
lines.push('## How you work');
|
|
22
41
|
lines.push('');
|
|
23
42
|
lines.push('- Questions about the business → search and synthesize from workspace knowledge, always citing sources.');
|
|
@@ -176,13 +195,13 @@ export const EXPERIENCES = [
|
|
|
176
195
|
{ id: 'see_capabilities', num: 2, name: 'See What\'s Possible', tier: 1, tierName: 'Orient & Equip', action: 'Type: "What can TACIT do for me?" — discover the full range of capabilities available to you.', signal: 'You know what TACIT can do and are ready to try it', tip: '' },
|
|
177
196
|
{ id: 'first_light', num: 3, name: 'First Light', tier: 1, tierName: 'Orient & Equip', action: 'Ask a question about your business — try "What do we know about [topic]?"', signal: 'First grounded answer drawn from your workspace knowledge', tip: '' },
|
|
178
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.' },
|
|
179
|
-
{ id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: '
|
|
180
|
-
{ id: 'connect_your_tools', num: 6, name: 'Connect Your Tools', tier: 1, tierName: 'Orient & Equip', action: '
|
|
181
|
-
{ id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report
|
|
182
|
-
{ id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: '
|
|
183
|
-
{ id: 'morning_brief', num: 9, name: 'Morning Brief', tier: 2, tierName: 'The Operating System', action: '
|
|
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
|
+
{ 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.' },
|
|
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.' },
|
|
184
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.' },
|
|
185
|
-
{ id: 'operating_rhythm', num: 11, name: 'Your Operating Rhythm', tier: 3, tierName: 'Agentic Mastery', action: '
|
|
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.' },
|
|
186
205
|
];
|
|
187
206
|
export function registerPrompts(server, getClientFn) {
|
|
188
207
|
server.prompt('assistant_system', 'System prompt for the TACIT workspace assistant — includes persona, progressive disclosure, and safety rules.', async () => {
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tacitai/mcp-server",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.25",
|
|
4
4
|
"description": "stdio MCP server wrapping Tacit /api/v1 REST/SSE API",
|
|
5
|
-
"license": "
|
|
5
|
+
"license": "UNLICENSED",
|
|
6
6
|
"repository": {
|
|
7
7
|
"type": "git",
|
|
8
8
|
"url": "git+https://github.com/scottkmcmillan/tacit.git",
|
|
@@ -38,8 +38,5 @@
|
|
|
38
38
|
"@types/semver": "^7.5.0",
|
|
39
39
|
"typescript": "^5.4.0",
|
|
40
40
|
"vitest": "^4.1.7"
|
|
41
|
-
},
|
|
42
|
-
"publishConfig": {
|
|
43
|
-
"access": "public"
|
|
44
41
|
}
|
|
45
42
|
}
|