What is an OAuth MCP connector?

Remote vs local MCP servers

A local MCP server runs on your machine (often launched with npx) and reads an API key from an environment variable. A remote MCP server runs in the cloud and is reached over HTTP. Remote servers can use OAuth, which is both more convenient and more secure because the credential never sits in a plaintext config file.

AetherWave offers both: a local npx install with an API key, and a remote OAuth connector at mcp.aetherwavestudio.com/mcp for clients that support it, such as Claude Desktop and Claude.ai.

Why OAuth is safer

With OAuth, the connector receives a scoped, revocable token tied to your account rather than a long-lived secret. You can revoke a connected app at any time from your profile, and there is no API key that could leak through a committed config file or a shared screen.

For end users the experience is simply: click Connect, approve, done.

Frequently Asked Questions

Do I still need an API key with an OAuth connector?

No. The OAuth connector handles authentication through your browser. You only need an API key for local installs that do not use the connector.

Can I revoke access later?

Yes. Connected apps can be revoked from your AetherWave profile under the Developer tab, which immediately invalidates the connector's token.