Should I use direct configuration or JSON import in Manus?

Either works and produces the same connection. Direct configuration lets you fill in fields; JSON import lets you paste a ready-made snippet. Both connect Vilix as a Custom MCP server.

Does context carry between Manus and my other AI tools?

Yes. Your memory is tied to your Vilix account, not the tool, so context moves automatically between Manus, ChatGPT, Claude, Cursor, and any other connected AI.

May 28, 2026 · 5 min read

How to use Vilix with Manus AI

Two ways to connect Vilix to Manus AI as a Custom MCP server, direct config or JSON import, so your autonomous agent carries the same memory, projects, and rules you built up across ChatGPT, Claude, and Cursor.

Manus is an autonomous agent, it goes off and does multi-step work on its own. The more it knows about your context going in, the better that work lands. By connecting Vilix as a Custom MCP connector, Manus gains your persistent cross-tool memory: the projects, tasks, decisions, and preferences you have already built up in ChatGPT, Claude, Cursor, and everywhere else. The agent stops starting from zero.

Manus supports custom MCP servers two ways. Pick whichever you prefer, the result is identical.

Open the Custom MCP screen

In Manus, go to Settings → Connectors → “+ Add Connectors” → the “Custom MCP” tab → “+ Add Custom MCP”. From there you have two options.

Option 1, Direct configuration

Name: Vilix
Transport: SSE / HTTP
Server URL: api.vilix.ai/mcp

Save, and authenticate when prompted.

Option 2, Import by JSON

Paste this into the JSON import field and save:

{
  "mcpServers": {
    "vilix": {
      "url": "https://api.vilix.ai/mcp",
      "transport": "sse"
    }
  }
}

Use it in natural language

Once connected, Manus lists Vilix’s tools alongside its prebuilt connectors. You do not call them by name, you just talk. Ask Manus to “pick up where I left off on the launch plan” or “check what tasks are still open on the billing project” and it reads from your Vilix memory to answer and act.

Because the memory lives in your Vilix account rather than in any one tool, the loop closes both ways. Work Manus does flows back into the same memory, so when you return to ChatGPT or Cursor later, that context is already there. This is what memory that works across tools looks like in practice: an autonomous agent that shares the same brain as the rest of your stack.

Frequently asked questions

How do I connect Vilix to Manus AI?

Go to Settings → Connectors → “+ Add Connectors” → Custom MCP → “+ Add Custom MCP”, then either fill in the direct config (Name Vilix, Transport SSE/HTTP, Server URL api.vilix.ai/mcp) or import the JSON snippet above and save.

Direct configuration or JSON import, which should I use?

Either works and produces the same connection. Use direct configuration if you prefer filling in fields; use JSON import if you already have the snippet handy.

What can Manus do once Vilix is connected?

Manus can read and write your persistent memory, projects, tasks, and user_rules in natural language, so an autonomous run starts with your full context and the results are saved back for every other tool to see.

Does my context carry between Manus and my other AI tools?

Yes. Your memory is tied to your Vilix account, not the tool, so context moves between Manus, ChatGPT, Claude, and Cursor automatically. You can try Vilix free for 7 days to set it up.