Foreword

What is Foreword?

Foreword (MCProxy) is an experimental proxy between MCP Clients and MCP Servers, allowing new features in the workflow between them. It is for developers working with the Model Context Protocol who need to add capabilities like logging, aggregation, blocking, or renaming of MCP resources, prompts, and tools.

How to use Foreword?

Foreword uses the same configuration file format as defined in the MCP Quickstart. In MCP Hosts like Claude Desktop, the configuration file should point toward Foreword, not the individual servers behind it. External modules can be added for extra features.

Key features of Foreword

• Logging all messages between MCP Client and Server
• Aggregating capabilities from multiple MCP Servers
• Blocking exposure of selected capabilities
• Renaming capabilities to avoid name collisions (disambiguation)
• Filtering or enriching textual content on the fly
• On-the-fly internationalization (i18n) via translation API or LLM

Use cases of Foreword

• Intercept and log all MCP traffic for debugging or auditing
• Combine tools from multiple servers behind a single proxy endpoint
• Restrict which tools or resources a client can access
• Resolve name conflicts when multiple servers expose same-named capabilities
• Translate content of MCP responses into a preferred language

FAQ from Foreword

What does Foreword do that a standard MCP server does not?

Foreword acts as a proxy that can modify and route MCP messages between a client and multiple servers, adding features like logging, blocking, renaming, or translation.

What are the dependencies or runtime requirements?

The README does not specify runtime requirements. The project is experimental and uses the MCP specification.

Where does data live in Foreword?

Data passes through Foreword; it does not store data persistently unless configured by an external module.

What are the known limits of Foreword?

The project is “very experimental and possibly totally useless”. It may contradict MCP design principles regarding cross-server interactions.

What transports or authentication does Foreword support?

The README does not mention specific transports or authentication mechanisms.