AI access

Your AI.
Powered by your web data.

Connect a project. Set the limits. Let your AI put the data to work.

01 / Choose

Start with one project.

Hosted OAuth asks you to choose one project. API keys can also be scoped to a project for local Model Context Protocol (MCP) or direct API access.

02 / Limit

Keep access in your hands.

Hosted MCP is read-only. API keys can have an expiry and finite collection allowance; review or revoke them from the dashboard.

03 / Connect

Keep credentials private.

OAuth stays in the sign-in flow. Store API keys only in your AI host’s secret settings, never in chat or source code.

Choose your tool

A clear path to your first connection.

Choose a tool, then configure access in your workspace.

Cursor

Use the locally built MCP server with a compatible local host, or call the REST API from your project. Store credentials in a local secret environment, outside source control.

Read the integration guide →

Other AI / API

Use a tool-capable agent with HTTPS access. Start with a read-only, expiring project key; enable collection only when you need it and set a finite allowance.

Create project access →

Hosted connections require enabled access and a client that supports remote MCP with OAuth. These guides do not grant access or imply an official directory listing.

Copy a safe starting prompt

This generic prompt contains no credentials. The dashboard can prepare project-specific instructions.

Help me connect Outway to this AI tool. Read https://outway.dev/docs/ai/ and identify whether this host supports remote MCP with OAuth. If hosted access is enabled, connect to https://api.outway.dev/mcp and choose one project; keep this connection read-only. Otherwise explain the secure local MCP or API setup. For API access, store the scoped key only in the host’s secret settings; never ask me to paste it into chat or commit it. Confirm scope and any collection allowance before starting work. Do not collect data unless I explicitly ask.

Build with the tools you use

Hosted OAuth.
Local MCP.

Use the hosted read-only OAuth endpoint for compatible remote MCP clients, or connect the locally built MCP server for broader, explicitly scoped collection workflows.

Hosted access uses https://api.outway.dev/mcp when enabled in the deployment. The client must support OAuth for remote MCP; directory approval is a separate process.

Open the developer guide →

Clear permissions, useful limits

Read-only is the default. Collection keys reserve requested units; their lifetime allowance does not renew. Revocation stops new authenticated requests but does not cancel queued work.

Project-bound keys cannot manage workspace billing or create recurring schedules, monitors or webhooks. Those actions stay with the signed-in user.