TerryAnn Core
Gateway + MCP Server for TerryAnn V2 - Medicare Journey Intelligence Platform.
Overview
TerryAnn Core provides:
- Gateway API: Conversation endpoint that handles user messages and orchestrates responses
- MCP Server: Tool definitions for cohort generation, journey simulation, and campaign execution
- Session Management: Conversation state and context tracking
Quick Start
# Install dependencies
pip install -e .
# Copy environment file
cp .env.example .env
# Edit .env with your settings
# Run locally
uvicorn app.main:app --reload --port 8080
API Endpoints
Gateway
POST /gateway/message- Send a message and get a responseGET /gateway/session/{session_id}- Get session detailsGET /gateway/tools- List available MCP tools
Health
GET /- Service infoGET /health- Health check
MCP Tools
| Tool | Description |
|---|---|
generate_cohort |
Generate a cohort based on targeting criteria |
get_cohort |
Retrieve an existing cohort |
simulate_journey |
Run Monte Carlo simulation on a journey |
compare_scenarios |
Compare multiple journey variations |
create_journey |
Create a new journey blueprint |
modify_journey |
Modify an existing journey |
optimize_journey |
Auto-optimize a journey for a goal |
push_to_crm |
Push data to CRM (Salesforce/HubSpot) |
schedule_campaign |
Schedule campaign execution |
Project Structure
terryann-core/
├── app/
│ ├── main.py # FastAPI entry point
│ ├── config.py # Settings
│ ├── gateway/ # Conversation handling
│ │ ├── router.py # Endpoints
│ │ ├── session.py # Session management
│ │ └── auth.py # Auth middleware
│ ├── mcp/ # MCP Server
│ │ ├── server.py # Tool registration
│ │ └── tools/ # Tool implementations
│ └── models/ # Pydantic schemas
├── tests/
├── Dockerfile
├── railway.toml
└── pyproject.toml
Development
# Install dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Lint
ruff check .
Deployment
Configured for Railway deployment via railway.toml.
railway up
Metadata
Release files for terryann-core 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| terryann_core-0.1.0.tar.gz | 38.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| terryann_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 77.7 kB
Release files / terryann_core-0.1.0.tar.gz
| Download URL | terryann_core-0.1.0.tar.gz |
|---|---|
| Size | 38.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
620a6bd21c33dd04541a9778a2607582347e494e50952df39b6cf6bd830244d5
|
|
BLAKE2b-256 checksum How to use checksums |
f9a669f6fecb727c886af804670610ef5d10b26a814a50724f0be77dbadcf9aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / terryann_core-0.1.0-py3-none-any.whl
| Download URL | terryann_core-0.1.0-py3-none-any.whl |
|---|---|
| Size | 39.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de2c7a37c73687e85f9cafa0bdf803f0b425db66332eafce8a8bd8ad09c5196a
|
|
BLAKE2b-256 checksum How to use checksums |
45ae336a72757ef4bd24ca05ad9e8ecd019a58963330fc212ca64d1cf2983f35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for terryann-core 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.