An MCP server that gives Claude Code your personal context
Stop re-introducing yourself to Claude Code, Codex and Hermes every session. Your AI coding assistant reads the notes, preferences and tasks you choose to share, and with the permissions you tick, it can write results back. Every change can be undone.
- Collaboration rules
- Tool preferences
- Approved notes
- Web clips
- Task list
- Life graph
Stop re-introducing yourself to your terminal
Coding context should not require constant repetition. Connecting Foremind via Model Context Protocol lets your terminal assistant start every task with your background already in place.
The blank slate in every new session
Every time you launch a fresh Claude Code or Codex session, you find yourself typing the same introductory paragraph. You outline your preferred Node runtime, your testing framework choices, your Git commit style, and the core purpose of your codebase. When you close the terminal, that background evaporates.
Manual copying between apps
Your project specs, architecture guidelines, and roadmap notes live inside your workspace. Whenever you want the assistant to solve a design challenge, you navigate away, highlight paragraphs of text, copy them, and paste them into the command line. This back-and-forth disrupts your flow and clutters your prompt history.
Personal context before the first line of code
With Foremind connected as an MCP server, you describe your goal in natural language. Before writing code, the assistant queries the get_user_context tool to check your shared collaboration guidelines and preferred tools. It searches approved notes and tasks directly through the protocol. You paste nothing.
You decide what it reads and what it may change
Your assistant reads only the profile categories and folders you allow. Creating, editing or deleting notes and tasks each needs its own tick on the authorization page, and every change it makes is listed under External changes in Settings, where you can undo it. Your main conversation history and Moments stay closed to it.
Set up external assistants in four steps
No API keys to copy and no passwords to type. You authorize in your browser after seeing exactly which permissions the assistant asks for.
Review sharing switches and exclusions
Sign in to Foremind and open Settings, then navigate to External assistants. Review Personal information you share. By default, Foremind shares your communication habits, communication preferences, tools you use, and what you are working on. You can place sensitive directories in Folders you do not share, which excludes them and all nested subfolders.
Copy the setup prompt into your assistant
Click Copy setup prompt on the External assistants screen. Send the complete text directly to Codex, Claude Code, or Hermes. The prompt includes your exact service address and the matching client commands. You do not need to look up endpoints or manage authentication secrets.
Contains dedicated service address and matching install command
Review permissions and click Allow
Your assistant executes its internal setup command and triggers a browser window. Check the assistant name and the permissions it asks for, and untick anything you do not want to give. Log in with the Foremind account whose context you wish to share, and click Allow to authorize access.
Reload session and verify access
When the confirmation screen indicates Connected, return to your terminal. Reload the connection or open a new session. Ask the assistant to query one shared item to verify that the handshake succeeded. The assistant confirms the connection name and scope without echoing your personal details back to you.
Commands for Codex, Claude Code, and Hermes
Each client supports straightforward command line checks and OAuth authorization. Use the setup prompt to obtain the exact service address for your account.
Inspect registration status and trigger browser authentication:
The add command containing your real service address is provided in the setup prompt. After authorization, reload your session to access tools.
Codex verification and login commands:
In headless servers, the command outputs a direct URL. Open that URL on any machine with a web browser to complete authorization.
Hermes connection management commands:
The setup prompt lets you save the usage agreement globally across projects or strictly for the current repository.
Clear boundaries: what assistants can read, what they can change, what stays private
Foremind is built around explicit consent. An assistant reads and writes only within the permissions you approve, and you can change them later without reconnecting.
Available with your consent
- Communication habits and preferences How you like to communicate and the kind of replies you prefer.
- Tools and active projects The tools you use and what you are working on right now.
- Approved notes and technical clips Technical documentation and reference material situated outside excluded folders.
- Task lists and life graph routes Your to-dos, plus the goals and routes in your life graph.
- Notes from conversations (opt-in toggle) Notes synthesized from your main dialogue or Council sessions remain hidden unless specifically enabled.
Closed to assistants, and permissions you did not give
- Main conversation history and Moments Your main conversation history and Moments are never open to external assistants.
- Excluded folders and subdirectories Any folder placed in your exclusion list is entirely omitted from search and retrieval operations.
- Permissions you did not tick Anything you left unticked on the authorization page stays off. You can change it later in Settings without reconnecting.
- Personal facts you have not confirmed An assistant can record lessons in Shared memory, but anything about you personally waits for your confirmation before it is saved.
- Computer access beyond the task’s setting Tasks assigned from the main conversation carry their own computer access: read only, write to the task folder, or write to a selected project.
Revoke access anytime with one click
To disconnect an assistant, open Settings, choose External assistants, locate the tool under Connected assistants, and click Disconnect. Access ends immediately. What the assistant already received cannot be recalled.
The usual way compared to Foremind MCP
See how personal context for AI coding agents transforms your daily terminal workflow.
| Dimension | The usual way | Foremind |
|---|---|---|
| Every new session | Re-explaining your stack, habits, and project background | Assistant loads your approved collaboration preferences before starting |
| Project context | Manually copying and pasting notes into the terminal | Assistant queries approved notes, clips, tasks, and life graph on demand |
| Multiple assistants | Writing separate setup prompts for each tool | Codex, Claude Code, and Hermes connect to the same Foremind context |
| Authorization | Copying and pasting API keys across environments | Review permissions in your browser and click Allow without handling keys |
| Privacy boundaries | Unclear visibility into what the assistant accesses | Granular toggles by category and folder, chat history and Moments stay locked |
| Disconnecting | Manually removing config files and revoking tokens | Click Disconnect in Settings to terminate access immediately |
Frequently asked questions
Everything you need to know about connecting Claude Code MCP, Codex MCP, and managing personal context.
How do I connect Claude Code to an MCP server with my own notes?
Open Settings in Foremind, select External assistants, and review the folders and personal information you want to share. Click Copy setup prompt and paste the complete text into Claude Code. Claude Code runs its installation command and opens a browser authorization tab. Review the requested permissions, sign in to your Foremind account, and click Allow. After the screen indicates Connected, reload your session to start referencing your notes.
Can the assistant change my data once it is connected?
Only if you tick those permissions on the authorization page, such as Create and edit notes or Create and edit tasks. Every change it makes is listed under External changes in Settings, External assistants, where Undo change restores what was there before. You can adjust permissions later without reconnecting.
Do I need an API key or a password?
No. You never need to look up API keys or generate access tokens. The setup prompt contains your service address and client configuration. Authentication happens securely in your web browser through standard OAuth where you manually confirm permissions.
Does it work with Codex and Hermes?
Yes. Both Codex and Hermes support Model Context Protocol connections. For Codex, verify status with codex mcp list and authorize using codex mcp login foremind --oauth-client-registration dcr (add --no-browser in a headless environment to view the authorization URL). For Hermes, check status with hermes mcp list and authorize using hermes mcp login foremind.
Can the external assistant see my chat history?
No. Your main conversation history and your personal Moments are never open to external assistants. Notes created from your main conversation or from Council deliberations remain hidden by default and only become readable if you manually enable the dedicated sharing toggle.
How do I keep a folder private?
Navigate to Settings, open External assistants, and add the folder path to Folders you do not share. Any excluded folder and all of its nested subfolders are instantly blocked from external search indexing and retrieval.
How do I disconnect, and what happens to what it already read?
Open Settings, click External assistants, find the client under Connected assistants, and click Disconnect. Access ends immediately and its next tool calls stop working. What it already received cannot be recalled.
It says connected, but my session has no Foremind tools. What now?
Reload the MCP client in your assistant or quit and restart your terminal session. If the tools still do not appear, confirm that your browser authorization completed successfully, or click Check again on the Foremind authorization screen.
Troubleshooting connection and scope issues
Follow these targeted checks if authorization stalls or an assistant cannot locate an expected resource.
Request expired or connection declined
Start the login command again from your assistant terminal and use the newly opened browser tab. Do not attempt to reuse stale authorization windows from previous attempts.
Screen indicates not confirmed yet
Check your terminal to verify that the assistant logged a successful connection message. Once confirmed in your command line, click Check again on the Foremind browser page.
Connected, but the session has no tools
Reload the MCP configuration in your assistant or restart the terminal window completely. Fresh terminal instances re-initialize the active tool registry automatically.
Connected, but a note or category is missing
Verify that you signed in with the correct Foremind account. Check your personal information toggles and review excluded folders. Notes derived from conversations require their own toggle.
Explore connected Foremind capabilities
The context your terminal assistant queries is nurtured by the rest of the Foremind workspace.
Give your AI coding assistant the context it needs
Stop repeating your tech stack and design conventions. Connect your workspace context via MCP and start coding with an assistant that knows your workflow.