Interface concept for MCP servers. is there something?

[Gelembjuk]

Pre-submission Checklist

• I have verified this would not be more appropriate as a feature request in a specific repository
• I have searched existing discussions to avoid duplicates

Your Idea

I would like to discuss the following.

I try to understand if MCP specification includes something like "server interfaces". When i say interfaces i mean something like interface in object oriented programming.
To explain what i mean i want to use the example.

Lets say there is some "MCP host" tool. Developers want to implement "memory" for this tool (or "LLM memory"). And adding MCP server for this looks good idea. It is little different from other tools working over MCP because not LLM decides when to call some tool, but it is hardcoded.
After each chat communication action some tool is called from "memory MCP server". And before each thinking it is called to "refresh memory" etc.
But after some time another "memory MCP server" appears created by another team. And it works better then the first.
Some users want to move to this new server.
But developers can not change the MCP host for each change. So, it would be nice to have this replaceable .

And here i come to the idea to have couple of "standard MCP servers".

For example, MCP server for "memory" must have the specific set of tools:

• "tool/add_to_memory"
• "resource/get_short_memory"
• "resource/get_long_memory"
• "tool/reorganize_memory"
• "tool/deep_reorganize_memory"

So, if anyone wants to build this plugin then just follows this "interface" and can offer his solution as a replacement to existent solutions.

Was it ever discussed? Should this be discussed or bad idea?

Scope

• Protocol Specification
• SDK Features
• Documentation
• Developer Experience
• Other

[Jeff-Bouchard]

+1 I think standard sets is a great idea.

[tadasant]

@toby has been working hard on an RFC similar to this for a while; tagging him in to share a link when he's ready

[toby]

Thanks @tadasant I have an RFC on Interfaces that I'd love to hear thoughts on. You can check it out here: https://docs.google.com/document/d/18ueGSeqd2sQEGcaR4spzf1NIxFtmcRFOR3F8dnhyYBc/edit?pli=1&tab=t.0#heading=h.w6nylr5u9xte

[Gelembjuk]

Yes. I think this is what i meant!

[Gelembjuk]

I have extended my idea for memory MCP interface in the blog post.

"Benefits of Using MCP to Implement AI Chat Memory"
https://gelembjuk.hashnode.dev/benefits-of-using-mcp-to-implement-ai-chat-memory.