Ethics of AIDocs
Back to site

Getting started

  • Overview

Remote MCP

  • Meeting users where they are: why we built MCP
  • Connect your AI client to Ethics of AI
  • Assistive, not autopilot: how interactive assessments stay yours
  • How we built a remote MCP server for Ethics of AI
On this page
  • Docs in this topic

Docs

Remote MCP

How Ethics of AI runs a remote Model Context Protocol server: the auth flow, the tool surface, and the deployment trade-offs behind it.

Docs in this topic

Concept5 min read

Meeting users where they are: why we built MCP

Browsers are one user surface; AI clients are another. MCP lets people engage with Ethics of AI from inside the client they already use.

Install guide3 min read

Connect your AI client to Ethics of AI

Add the Ethics of AI MCP connector in Claude Desktop, on claude.ai, or on mobile, so Claude can drive assessments and read your account on your behalf.

Concept6 min read

Assistive, not autopilot: how interactive assessments stay yours

Claude can explain each assessment question in plain English, but it cannot pick or write your answer. This is how that line is drawn, and why it still needs your trust.

Implementation9 min read

How we built a remote MCP server for Ethics of AI

Why remote MCP, how DCR with Clerk works, why we wrap our existing API instead of going pure-MCP, and why API Gateway plus Lambda plus FastMCP is the right surface for us.

On this page

  • Docs in this topic