portfolio-agent
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@portfolio-agenttell me who I'm logged in as"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
portfolio-agent
Portfolio tracker with an analysis agent and MCP access. FastAPI, Postgres (Neon), WorkOS AuthKit (GitHub or Google), Claude.
Local setup
Requires Python 3.12. Use the project virtualenv at .venv (not a base Anaconda env).
cd portfolio-agent
python3.12 -m venv .venv
source .venv/bin/activate
pip install -U pip
pip install -r requirements.txt
cp .env.example .env
# Fill in every value in .env (see below)
alembic upgrade head
uvicorn app.main:app --host localhost --port 8000On startup the process prints:
WorkOS redirect URI— register this under WorkOS → RedirectsMCP resource URL— register this under WorkOS Connect → Resource Indicators (and set as default)
Open http://localhost:8000.
Related MCP server: auth0-whoami-mcp-template
Environment variables
Name | Purpose |
| Public origin, no trailing slash. Local: |
| Comma-separated browser origins allowed to call |
| Neon pooled Postgres URL ( |
| Neon direct URL for Alembic ( |
| WorkOS API key |
| WorkOS client id |
| Fernet key, min 32 chars: |
| e.g. |
WorkOS checklist (short)
Enable AuthKit; enable both GitHub and Google as sign-in methods.
Redirect URI = printed
WorkOS redirect URI(/callback).Sign-out URI =
BASE_URL(or/).Initiate login URI =
BASE_URL/login.Connect → enable CIMD and DCR; add MCP resource URL; set as default.
Render
See render.yaml. Start command runs migrations then Uvicorn on $PORT. Set the same env vars in the Render dashboard; BASE_URL must be the public HTTPS URL.
Health
GET /healthz — plain liveness (not the MCP endpoint).
MCP
Streamable HTTP at /mcp, protected by WorkOS AuthKit (AuthKitProvider). Tool available today: whoami.
This server cannot be deployed
Maintenance
Related MCP Connectors
Minimal streamable HTTP MCP server used for owned-account registry connectivity tests.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP client interaction via streamable HTTP, providing example tools (echo, getPostsByUser) and resources (posts, users) with pluggable authentication providers.6MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes an authenticated Streamable HTTP endpoint with a whoami tool returning safe claims for the current Auth0 user.MIT
- AlicenseNot gradedqualityBmaintenanceEnables end-to-end testing of OAuth authorization for an MCP server, exposing scoped tools like whoami and echo over streamable HTTP.ISC
- FlicenseNot gradedqualityCmaintenanceEnables querying a fictional internal IT asset service to look up users and devices, including finding which laptop is assigned to a user, through MCP tools over Streamable HTTP.1-