Connected Tools
Start with Ewe Note, connect supported AI clients, or build a focused app on top of the same user-owned data layer.
Signed-out preview
Tools are visible here before sign-in. Actual MCP setup flows, OAuth prompts, token generation, status badges, and revoke controls stay behind the authenticated app shell.
Production testing has verified token bootstrap, core MCP operations including search and Agent Journal writes, and Claude Desktop integration through HTTP SSE transport. OAuth client validation and non-Claude-Desktop client proofs remain pending until those specific flows are verified.
App sign-in and notes access grant
The local-first note-taking proof point for user-owned rooms. Rich imported-vault navigation and Obsidian-style embed polish are still in progress.
Local save flow is verified; imported-vault UX follow-ups are queued.
Token-backed MCP setup
Local desktop setup using the Eweser MCP server and token-backed access.
Production-verified token setup with full MCP operation coverage.
OAuth remote MCP
Remote HTTP MCP connection through the authenticated Eweser OAuth path.
Hosted production validation is pending before we treat this as proven.
OAuth remote MCP
ChatGPT connector setup through the authenticated Eweser MCP endpoint.
Hosted production validation is pending before we treat this as proven.
Token-backed setup
Token-backed agent access for development workflows that need scoped data reads.
Uses the same token path; separate Copilot client proof is pending.
Token-backed setup
Token-backed setup for Codex workflows that need permissioned Eweser data.
Uses the production-verified token-backed MCP setup path.
OpenClaw MCP setup
OpenClaw remote HTTP MCP setup using streamable-http and a scoped Eweser token.
Uses the same token path; separate OpenClaw client proof is pending.
