Connect tools with MCP
Add focused integrations without flooding every conversation.
Reviewed 6 October 2026 · 2 min read
Import example project ↗Two named conversations, shared files, revisions and a preview.
Before you start
MCP connects AI applications to tools exposed by another program/service. An SDK provides software-development components; it is not the same thing.
A server can read/change data within its permissions. Understand its source and what information it receives.
Step by step
- Open Extensions/MCP in a supported desktop build.
- Choose a setup guide or configure a local executable or HTTPS endpoint.
- Install compatible editor/server components and use credential fields where required.
- Enable it for the intended conversation and begin with a small read-only check.
- Disable unused connections.
Try this
Example request
Find a Godot integration compatible with this engine version. Explain access, pin the selected version, connect only to this project conversation and verify inspection before editing.
Check the result
- Editor/plugin and server versions match.
- Only relevant connections are enabled.
- Errors and evidence are visible.
- Community integrations are labeled as such.
If something goes wrong
Check executable path, runtime, arguments and logs. Do not paste access tokens into chat.
A running server may still need an open editor, project or signed-in account.
Your screen may differ by platform and version. Check availability or get help.