Frequently Asked Questions

Frequent questions about MCI

What is MCI actually providing?

Among others, MCI provides:

• Efficiency: MCI is built on researched and proven concepts, our methodology assures effective token usage, cutting down costs, preventing context bloat and making interactions faster.
  • MCP code execution
  • MCP tool search
• Agnosticism: MCI is protocol-agnostic at the end-service layer. MCI exposes an HTTP REST API, while adapter modules connect to end services over their native protocols and standards.
• Availability: MCI is infrastructure-agnostic and can run in serverless, IoT, or clustered environments.
• Observability: MCI provides built-in tool call observability for users and administrators.
• Security and Permissions: MCI supports granular tool call security and permission controls.
• Better Developer Experience: To make an existing service usable on MCI, you do not need to write new server code. You can provide a definition such as OpenAPI and register it through adapter modules.

What makes MCI more secure and observable?

MCI provides an interception layer for tool calls. Requests can be inspected to block, redirect, or log actions before execution. This supports policy enforcement and audit workflows.

What does the “code” look like?

MCI doesn’t force a proprietary language (DSL) on you. It uses environment modules that translate definitions into standard libraries.

This means models can write tasks in Python, JavaScript, or any language the runtime supports.

Is MCI execution stateful?

Yes. While MCP relies on the model’s limited context window to “remember” state, MCI shifts state management to the code and the runtime. This keeps the model’s context clear and makes tool interactions significantly more reliable.

Does this mean I cant use MCP?

No. You can use MCI alongside existing MCP servers. You can also connect MCI directly to endpoints when an MCP middle layer is not needed.

Why not just extend MCP to do this?

MCP is a communication standard. Incorporating these features would require redefining its core principles, likely breaking existing implementations. While third-party wrappers could add some of this functionality to MCP, they cannot match the native security and efficiency of a purpose-built control interface.

Is MCI opinionated about hosting or deployment?

No. MCI is infrastructure-neutral. Whether you are running on-prem, in the cloud, or on embedded devices, MCI is compatible as long as the host environment can enforce the execution contract.