Epiphani
com.epiphaniPublished by epiphani.comOfficial publisherv0.1.6Updated Oct 26, 2026
One connector for every Epiphani app you use: tasks, health, money, travel, documents and more.
Overview
Remote Epiphani connector that lets an assistant work across the Epiphani apps you use, including tasks, health, money, travel and documents.
- What you can do
- No tool list is published, so capabilities are known only from the description.
- It is presented as a single connector covering every Epiphani app a user has.
- Named areas include tasks, health, money, travel and documents.
- What the assistant can actually read or change in each app is not documented.
- When to use it
- Worth considering if you already use Epiphani apps and want an assistant to reach that data through one connection instead of separate integrations. Because the tool list is unpublished, check the server's own documentation before relying on it for specific actions.
- Requirements
- A remote streamable HTTP endpoint at mcp.epiphani.com; nothing to install locally. OAuth authentication is required, so you need an Epiphani account and must complete the OAuth sign-in flow. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Epiphani in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.epiphani%2Fconnector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"epiphani": {
"type": "http",
"url": "https://mcp.epiphani.com/mcp"
}
}
}Tools
0Version history
1- v0.1.6LatestOct 22, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.