Repository navigation
Add integrations for coding environments to understand Exosphere docs #476
Description
Activity
- addeddocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomers
on Oct 9, 2025 Hi @nk-ag if this is something related to documentation could you please assign me with further details?
Hey @nk-ag, I’d love to take this up and add the integration.
Could you please assign this issue to me?@DevJin27 @Siddharthablog this is an open ended exploration, the whole Idea is to make it easier for people to work with exosphere project.
alright! thankyou
I will raise a pr for the same once I am done with classes@DevJin27 are you working on this??
@NiveditJain If no one is working on this, please assign it to me
@NiveditJain I am working on this.
Reacted by Nivedit Jain@Brijesh-Thakkar okay
Proposed Approach for the Integrations Menu
I'd like to take up this issue and am sharing my proposed plan before starting development.
The goal is to add an integrations menu to the Exosphere documentation (built with MkDocs + Material) to help users seamlessly use the docs inside AI tools and MCP-compatible editors like Cursor and VS Code.The design will follow patterns used by platforms like Restack AI, adapted to Exosphere’s ecosystem.
Planned Behavior for Each Integration
1. Open in ChatGPT
- Opens ChatGPT in a new tab.
- Prefills a prompt with:
- the page title
- the page URL
- a short instruction such as:
“Summarize this documentation page and explain the key concepts.”
- If the platform doesn’t support prefilled prompts through URLs, we will copy the prompt to the clipboard as a fallback.
2. Open in Claude
- Same behavior as Open in ChatGPT but targeted to Claude.
- Clipboard fallback included.
3. Copy Page
- Copies the full page content by:
- selecting the main content area
- converting it from HTML → clean Markdown
- including the page URL at the top or bottom
- Markdown improves readability and generates better results when pasted into AI models.
4. Copy MCP Server
- Copies the official Exosphere MCP server URL to the clipboard.
- This is needed to register Exosphere as an MCP server inside tools like Cursor, VS Code, ChatGPT Desktop, Continue.dev, etc.
5. Connect to Cursor
This does not open or clone the repo.
Instead, when clicked, it will:
- Open a simple modal.
- Show a short explanation of what MCP integration is.
- Present the steps for adding the MCP server in Cursor:
- Open Cursor → Settings → MCP Servers
- Click Add Server
- Paste the provided JSON snippet
- Provide a Copy Config button to copy the MCP JSON snippet.
- No deep links will be used — only instructions + a copyable config.
This improves onboarding for users working in Cursor.
6. Connect to VS Code
Similar workflow to Cursor:
- Opens a modal.
- Shows steps for integrating the MCP server using a VS Code MCP client extension.
- Provides a snippet to add to VS Code's
settings.json:
"mcp.servers": { "exosphere": { "url": "<MCP_SERVER_URL>" } }
@NiveditJain Please suggest any changes that are needed in my approach.
I also have a few questions I need clarified before I start implementing:
1. MCP server URL
- What is the official Exosphere MCP server URL?
- Are there different endpoints for development / staging / production?
2. ChatGPT / Claude prompt content
- Should the prefilled prompt include only the page URL, or can it also include a short instruction such as “Summarize this documentation page and explain the key concepts” so users get a quick overview?
My default: include title + URL + a short “summarize” instruction (helps first-time readers).
3. UI placement
- Where should the integrations dropdown live: in the navbar, as a floating button, or next to the page title?
My recommendation: navbar dropdown for a consistent, non-intrusive experience.
4. Cursor / VS Code modal content
- For the “Connect to Cursor” / “Connect to VS Code” flows, do you prefer the modal to be:
- Minimal (short instructions + copyable config), or
- Step-by-step (detailed onboarding for beginners)?
My recommendation: minimal by default, with a link to a full step-by-step guide for beginners.
5. Copy Page format
- My plan is to copy both:
- the page content converted to clean Markdown, and
- the page URL.
Is that acceptable, or would you prefer a different format?
@Brijesh-Thakkar I am reviewing this, will keep you posted.
Reacted by Brijesh ThakkarHi @NiveditJain ,
Just following up on the approach I shared earlier — wanted to check if it looks good to proceed with, or if you’d suggest any changes before I start implementing.
Happy to adjust based on your feedback. Thanks!
Add similar integration: