MCP 2025-06-18 specification

bza · September 15, 2025, 12:11pm

Can 2025-06-18 specification of MCP Client can be implemented ?

The idea is:

The Idea is to be compatible with 2025-06-18 spec by simply bounce client library : @modelcontextprotocol/sdk

My use case:

We are implementing MCP server modelcontextprotocol/php-sdk and as it is a new library, it’s not compatible with old specifications

I think it would be beneficial to add this because:

As MCP support protocol negotiation, it’s a no risk operation to keep up to date this library

Any resources to support this?

github.com/n8n-io/n8n

packages/%40n8n/nodes-langchain/package.json

master


      
          "@langchain/groq": "0.2.3",
          "@langchain/mistralai": "0.2.1",
          "@langchain/mongodb": "^0.1.0",
          "@langchain/ollama": "0.2.3",
          "@langchain/openai": "catalog:",
          "@langchain/pinecone": "0.2.0",
          "@langchain/qdrant": "0.1.2",
          "@langchain/redis": "0.1.1",
          "@langchain/textsplitters": "0.1.0",
          "@langchain/weaviate": "0.2.0",
          "@modelcontextprotocol/sdk": "1.12.0",
          "@mozilla/readability": "0.6.0",
          "@n8n/client-oauth2": "workspace:*",
          "@n8n/config": "workspace:*",
          "@n8n/di": "workspace:*",
          "@n8n/errors": "workspace:^",
          "@n8n/json-schema-to-zod": "workspace:*",
          "@n8n/typeorm": "0.3.20-12",
          "@n8n/typescript-config": "workspace:*",
          "@n8n/vm2": "3.9.25",
          "@pinecone-database/pinecone": "^5.0.2",

Are you willing to work on this?

I can make a PR if needed