Connect your coding agent to AiSCent.
AiSCent exposes its App Store workflows to compatible coding agents through MCP. Connect the server once, then use it from the coding assistant you already work in. The model choice belongs to your client or account; AiSCent provides the tools.
Client compatibility and setup
Claude Code
SupportedUse the MCP install flow in AiSCent, or follow the command it provides. Verify with `claude mcp list` and `/mcp`.
Official setup documentation ↗Cursor
SupportedAdd AiSCent from its MCP install flow or add its provided server entry in Cursor Settings → MCP. Restart or reload tools after changes.
Official setup documentation ↗Windsurf
SupportedUse the AiSCent install flow, then confirm the server is enabled in Windsurf’s MCP settings.
Official setup documentation ↗VS Code / GitHub Copilot
MCP-compatibleUse the server details provided by AiSCent in VS Code’s MCP: Add Server flow or `.vscode/mcp.json`; enable it in Copilot Agent mode.
Official setup documentation ↗Codex
MCP-compatibleUse the AiSCent install flow or add its remote/local server details to Codex MCP settings. Confirm with `codex mcp list`.
Official setup documentation ↗ChatGPT
Workspace setupChatGPT can connect to remote MCP apps. A workspace admin or authorized developer must add the endpoint, scan tools, and configure access. Availability depends on plan and workspace settings.
Official setup documentation ↗Gemini CLI / Antigravity
MCP-compatibleConnect using the server details AiSCent provides. Gemini's supported MCP setup varies by client; verify the connected server in that client's MCP settings.
Official setup documentation ↗What “all frontier models” means
MCP connects an agent client to tools; it does not bind AiSCent to one model vendor. A client may offer several models and change that list over time. Choose any model exposed by your client that supports tool use, then enable AiSCent for that session. The client handles model availability, account access, and model-specific tool calling.
Set up safely
Start from AiSCent’s current install flow so you use the correct server address, transport, and authentication method. Do not copy credentials into shared project configuration. Keep App Store Connect keys in AiSCent’s supported secure credential store, review proposed changes, and retain the final submission decision.
If your client cannot connect, check that MCP is enabled, reload the client after installation, complete any sign-in prompt, and confirm that AiSCent tools appear in the client’s tool list. For account or product access, contact AiSCent support.