MCP setup

Odysseus MCP setup guide

MCP gives Odysseus tools. That can mean filesystem access, GitHub context, search, databases, calendars, and more. The right setup is useful, narrow, and easy to audit.

Start with one MCP server

Do not connect every tool on day one. Start with a single low-risk server, confirm Odysseus can call it, then expand permissions gradually.

Filesystem MCP

Filesystem tools are powerful but risky. Restrict the root folder to a test project, not your entire drive.

D:\Projects\odysseus-test
/home/user/projects/odysseus-test

GitHub MCP

GitHub tools are useful for issues, pull requests, and repository context. Use the narrowest token scope that works for your task.

Use read-only access first.
Avoid organization-wide tokens for local tests.
Rotate tokens if they were pasted into a test config.

Database MCP

For databases, start read-only and use a sample database. A coding or research agent should not have production write access during early tests.

Search and research MCP

If you use search tools for Deep Research, require citations and dates in the prompt. Search access is not the same as source quality.

Set up SearXNG for Deep Research

MCP safety checklist

Connect one tool at a time.
Use read-only permissions first.
Keep secrets outside public repositories.
Review logs after tool calls.
Disable unused MCP servers.