
Listed below are the built-in capabilities of Openprise’s MCP Factory
Connection and Context
| NAME | WHAT IT DOES | EXAMPLE PROMPT |
| connect | Logs Claude into an Openprise environment. Runs once at the start of a session. | "Connect me to Openprise" |
| disconnect | Logs out of Openprise, clearing the cached session. | "Log me out" |
| switch_tenant | Switches the active customer tenant within the same pod. | "Switch over to the ABC Company tenant" |
| switch_pod | Switches to a different Openprise pod entirely. | "Actually, switch me to the west2 environment instead." |
| whoami | Shows which account, pod, and tenant are currently active. | "Which Openprise account and tenant am I connected to right now?" |
Data Search & Discovery Tools
| NAME | WHAT IT DOES | EXAMPLE PROMPT |
| list_datasources | Lists available data sources in the tenant. | "What data sources do we have available in this tenant?" |
| get_datasource_attributes | Returns the exact field names available on a given data source. | "What fields are available on the Contacts data source?" |
| get_field_values | Pulls all distinct values that exist for a specific field. | "What are all the different values that show up in the Lead Status field?" |
| search_data | Runs a filtered query against a data source and returns matching records - can filter by tags. | "Find all contacts in California that don't have a phone number on file." |
| list_tags | Lists the tags/labels used in the tenant. | "What tags or categories are set up in this tenant?" |
Job Tools
| NAME | WHAT IT DOES | EXAMPLE PROMPT |
| list_pipelines | List jobs, or fetch details on a specific one. | "What jobs do we have configured with the “Enrichment” label?" |
| get_pipeline_sample | Retrieves an example input/output payload for a jobs. | "Show me an example of what the Email Validation job expects and returns." |
| get_pipeline_api_info | Retrieves the public API endpoint and auth details for a job. | "What's the API endpoint for the Lead Enrichment job?" |
| invoke_pipeline | Calls a job's API with input records and returns the enriched output. | "Run these 50 leads through the Enrichment job and show me the results." |
| list_jobs | Lists configured data jobs, optionally filtered by tag or API status. | "What data jobs are API-enabled?" |
| list_job_run_history | Returns the run history of a job. | "Show me the run history for the Nightly Dedupe job." |
| get_job_run_details | Drills into one specific run with a per-task breakdown. | "For that run on Tuesday, break down what happened task by task." |
Bot Tools
| NAME | WHAT IT DOES | EXAMPLE PROMPT |
| list_bots | Lists bots in the tenant, filterable by tag or status. | "What bots do we have and which ones are currently disabled?" |
| get_pinned_bots | Retrieves the tenant's "pinned" saved bot reports. | "Show me the bot reports we've pinned as most important." |
| get_bot_health | Gives overall health status across bots over a chosen time window. | "How healthy have our bots been over the last 24 hours?" |
| get_bot_run_details | Fetches recent run history/status summaries for specific bots. | "What's the latest run status for the Lead Routing bot?" |
| get_bot_run_history | Returns per-run history for a single bot and flags statistical outliers. | "Show me the run history for the Data Cleanse bot and flag anything unusual." |
| get_bot_run_entity_details | Shows every job that ran within one specific bot run. | "For that slow run yesterday, show me every job that ran within it." |
| get_bot_errors | Guided, multi-step investigation from bot → run → specific error records. | "Which bots have had errors recently?" (then, conversationally: "Tell me more about that one" → "What actually failed in that run?") |