feat: Add Grok Connectors / BYO MCP integration guide

[vincenzopalazzo]

Summary

xAI recently launched Grok Connectors, which allow Grok to read/write external services. One of the supported connector types is BYO MCP (Bring Your Own Model Context Protocol server).

OpenMemory already ships an MCP server with tools like openmemory_query, openmemory_store, openmemory_get, openmemory_delete, and openmemory_list — making it a natural candidate for Grok's BYO MCP integration.

Problem

There is no documentation, configuration guide, or tested flow for connecting OpenMemory's MCP server to Grok via the BYO MCP connector. Users who want Grok to have persistent memory through OpenMemory currently have no clear path.

Requested Changes

1. Documentation: Add a guide (e.g., docs/grok-integration.md) explaining how to:

   • Expose the OpenMemory MCP server publicly (deployment considerations, HTTPS, auth)
   • Configure the Grok BYO MCP connector to point to the OpenMemory MCP endpoint
   • Required environment variables and any compatibility notes

2. Compatibility verification: Test that Grok's BYO MCP client can successfully discover and call the OpenMemory MCP tools (openmemory_query, openmemory_store, etc.)

3. Auth considerations: Document how to secure the MCP endpoint for Grok access (e.g., OM_API_KEY, TLS termination)

Context

• OpenMemory MCP server code (JS): packages/openmemory-js/src/ai/mcp.ts
• OpenMemory MCP server code (Python): packages/openmemory-py/src/openmemory/ai/mcp.py
• MCP tools exposed: openmemory_query, openmemory_store, openmemory_get, openmemory_delete, openmemory_list
• MCP transports supported: StreamableHTTP + stdio (JS), stdio (Python)

References

• Grok Connectors announcement
• Grok Connector docs
• MCP specification

[nullure]

Thanks for the suggestion! This will be added to OpenMemory v1.3

[vincenzopalazzo]

In the meantime, Grok fixed the no auth connection