Codex CLI
Codex detects OAuth discovery and opens your browser to authorize.
codex mcp add nexusol --url https://www.nexusol.app/api/mcpNexusol MCP connects compatible personal agents to Nexusol ecosystem intelligence, synthesized news, and your account profile. You authorize access in the browser; passwords and API keys are never copied into agent configuration.
Quickstart
Add the remote server URL to your MCP client. The client discovers Nexusol OAuth automatically, opens a browser, and asks you to approve the requested read scopes.
https://www.nexusol.app/api/mcpUse the URL in your agent's MCP settings.
Authenticate with the same Google or X account you use on Nexusol.
Review the requested scopes, then allow or deny the connection.
Personal agents
Codex detects OAuth discovery and opens your browser to authorize.
codex mcp add nexusol --url https://www.nexusol.app/api/mcpAdd the HTTP server, start Claude Code, then use /mcp to authenticate.
claude mcp add --transport http nexusol https://www.nexusol.app/api/mcp
claude
/mcpAdd this project-level configuration, then choose Needs login in Cursor MCP settings.
{
"mcpServers": {
"nexusol": {
"url": "https://www.nexusol.app/api/mcp"
}
}
}Enable Developer mode, create a custom connector named Nexusol, use the endpoint above, and select OAuth authentication.
Use an OAuth-capable MCP client provider. HTTP is the recommended remote transport.
import { createMCPClient } from "@ai-sdk/mcp";
const client = await createMCPClient({
transport: {
type: "http",
url: "https://www.nexusol.app/api/mcp",
authProvider: yourOAuthClientProvider,
},
});
const tools = await client.tools();Tool reference
search_projectsSearch active projects in the Nexusol ecosystem directory.
ecosystem:readget_projectGet one ecosystem project by its exact slug.
ecosystem:readlist_latest_newsList recent synthesized Solana news, with optional search.
news:readget_articleRead one Nexusol news article by slug.
news:readget_my_profileRead your public-facing Nexusol profile fields.
profile:readSecurity
Compatible clients discover OAuth and store their own authorization securely.
Each tool checks its required scope before returning data.
This first version cannot create, edit, delete, trade, post, or message.
The profile tool returns public-facing fields only—not provider IDs or internal auth records.
Only connect the canonical endpoint shown above. During authorization, verify that your browser is on nexusol.app before approving access.
Help
Open the client's MCP settings and choose Login, Authenticate, or Reconnect. The Nexusol server intentionally returns an OAuth challenge before authorization.
Normal Nexusol sign-in finishes in the app. Start the MCP connection again from your agent so it can attach its signed OAuth request.
Disconnect and reconnect the server, then approve the requested scope. Denied scopes are never silently added later.
Confirm the client supports remote HTTP MCP and OAuth. Older clients that only support local stdio servers cannot connect directly.
This guide uses the task-first structure common to OpenAI and Vercel docs: quickstart first, client-specific examples, reference, security, then troubleshooting. It is built with the project's existing Next.js and Tailwind stack. If the documentation grows into many pages, Fumadocs is the recommended next layer for MDX content, search, sidebar navigation, and generated page trees.