From 9e92f0fa32c32e30980c19f1c4061a078d395cca Mon Sep 17 00:00:00 2001 From: olaservo Date: Sat, 14 Jun 2025 17:37:55 -0700 Subject: [PATCH 1/3] Update completions --- src/index.ts | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/index.ts b/src/index.ts index 12f56c2..156f187 100644 --- a/src/index.ts +++ b/src/index.ts @@ -62,7 +62,7 @@ class Cache { const SCHEMA_URL = `https://raw.githubusercontent.com/modelcontextprotocol/specification/refs/heads/main/schema/${VERSION}/schema.json`; // Suggested topics -const TOPIC_COMPLETIONS = ['tools', 'prompts', 'resources', 'roots', 'sampling', 'transports', 'authorization', 'why not just use http?', 'why does this protocol need to exist?']; +const TOPIC_COMPLETIONS = ['tools', 'prompts', 'resources', 'roots', 'sampling', 'transports', 'authorization', 'why not just use http?', 'security best practices', 'cancellation', 'progress reporting', 'server utilities', 'client utilities']; // Include all prompt names here const EXPLAIN_PROMPT = 'explain'; const EVALUATE_SERVER_PROMPT = 'evaluate_server_compliance'; @@ -158,9 +158,7 @@ const serverCapabilities: ServerCapabilities = { const server = new Server( { name: 'mcp-advisor', version: '0.3.2' }, { capabilities: serverCapabilities, - instructions: `I am a Model Context Protocol (MCP) documentation expert that provides comprehensive access to the MCP specification and helps evaluate server implementations for compliance. - I have access to the complete MCP specification across multiple versions (${SUPPORTED_VERSIONS.join(', ')}) including schemas, architecture docs, protocol details, and implementation guides. I can explain any MCP concept in detail with authoritative references and evaluate server code against the specification requirements. - Default version: ${VERSION} (can be overridden per request)` + instructions: `Workflow: 1) Use 'explain' prompt for understanding MCP concepts before implementation, 2) Use 'evaluate_server_compliance' prompt to validate existing server code against specification requirements. Always specify version parameter when comparing across MCP versions or working with specific spec releases. Resource templates support version-specific access - use {version} parameter for precise specification targeting. Performance: Content is cached for 1 hour; initial requests may take 5-10 seconds for complete specification fetching. Limitations: Requires network access to modelcontextprotocol.io; falls back to expired cache on network failures. Supported versions: ${SUPPORTED_VERSIONS.join(', ')} (default: ${VERSION}).` } ); From 9de1eccbfad7958bb814a6618985fc594627f830 Mon Sep 17 00:00:00 2001 From: olaservo Date: Sat, 14 Jun 2025 17:40:27 -0700 Subject: [PATCH 2/3] Update instructions --- src/index.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/index.ts b/src/index.ts index 156f187..46bf70d 100644 --- a/src/index.ts +++ b/src/index.ts @@ -158,7 +158,7 @@ const serverCapabilities: ServerCapabilities = { const server = new Server( { name: 'mcp-advisor', version: '0.3.2' }, { capabilities: serverCapabilities, - instructions: `Workflow: 1) Use 'explain' prompt for understanding MCP concepts before implementation, 2) Use 'evaluate_server_compliance' prompt to validate existing server code against specification requirements. Always specify version parameter when comparing across MCP versions or working with specific spec releases. Resource templates support version-specific access - use {version} parameter for precise specification targeting. Performance: Content is cached for 1 hour; initial requests may take 5-10 seconds for complete specification fetching. Limitations: Requires network access to modelcontextprotocol.io; falls back to expired cache on network failures. Supported versions: ${SUPPORTED_VERSIONS.join(', ')} (default: ${VERSION}).` + instructions: `Workflow: 1) Use 'explain' prompt for understanding MCP concepts before implementation, 2) Use 'evaluate_server_compliance' prompt to validate existing server code against specification requirements. Always clarify expected spec version and provide the version parameter when working with specific spec releases. Resource templates support version-specific access - use {version} parameter for precise specification targeting. Performance: Content is cached for 1 hour; initial requests may take 5-10 seconds for complete specification fetching. Limitations: Requires network access to modelcontextprotocol.io; falls back to expired cache on network failures. Supported versions: ${SUPPORTED_VERSIONS.join(', ')} (default: ${VERSION}).` } ); From 883c04ff75f961029b785806873a7e1d0442ea3a Mon Sep 17 00:00:00 2001 From: olaservo Date: Sat, 14 Jun 2025 17:41:15 -0700 Subject: [PATCH 3/3] Bump version --- package-lock.json | 4 ++-- package.json | 2 +- src/index.ts | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/package-lock.json b/package-lock.json index a84eb0c..73dfb2f 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "mcp-advisor", - "version": "0.3.2", + "version": "0.3.3", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "mcp-advisor", - "version": "0.3.2", + "version": "0.3.3", "license": "ISC", "dependencies": { "@modelcontextprotocol/sdk": "^1.11.4", diff --git a/package.json b/package.json index 842cded..b72aba0 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "mcp-advisor", - "version": "0.3.2", + "version": "0.3.3", "description": "MCP Server to assist LLMs and humans on Model Context Protocol (MCP) spec compliance and understanding", "main": "dist/index.js", "types": "dist/index.d.ts", diff --git a/src/index.ts b/src/index.ts index 46bf70d..51c425a 100644 --- a/src/index.ts +++ b/src/index.ts @@ -156,7 +156,7 @@ const serverCapabilities: ServerCapabilities = { }; const server = new Server( - { name: 'mcp-advisor', version: '0.3.2' }, + { name: 'mcp-advisor', version: '0.3.3' }, { capabilities: serverCapabilities, instructions: `Workflow: 1) Use 'explain' prompt for understanding MCP concepts before implementation, 2) Use 'evaluate_server_compliance' prompt to validate existing server code against specification requirements. Always clarify expected spec version and provide the version parameter when working with specific spec releases. Resource templates support version-specific access - use {version} parameter for precise specification targeting. Performance: Content is cached for 1 hour; initial requests may take 5-10 seconds for complete specification fetching. Limitations: Requires network access to modelcontextprotocol.io; falls back to expired cache on network failures. Supported versions: ${SUPPORTED_VERSIONS.join(', ')} (default: ${VERSION}).` }