Povento Connect
Connect your coding agent to Povento to inspect portfolio and project context, discover app capabilities, and prepare scoped setup plans.
Documentation
Make your next move with your agent
Turn a business goal into a scoped plan across your portfolio.
Useful context. Deliberate permission.
Povento MCP is a contract-based agent access layer, not a private repository shortcut. It never gives an agent provider secrets, static API keys, or a way around account, project, environment, capability, or permission checks. Available, selected, configured, provisioned, verified, and released stay distinct.
Reads, project control, and bounded analytics.
Writes require confirmation
01
Account and portfolio
owner.list_portfolios · owner.get_portfolio
Inspect the portfolios and portfolio summaries available to the authenticated owner.
02
Project inventory
owner.list_projects · owner.get_project
List and inspect projects within the effective account and membership scope.
03
Project context
owner.get_project_context · owner.get_project_configuration · owner.get_project_passport
Read a bounded project-context passport and the exact public runtime footprint without secrets or unbounded customer or provider content.
04
Web analytics
owner.get_project_analytics · owner.configure_web_analytics_source
Inspect bounded project analytics or, with runtime write permission and confirmation, create an origin-restricted browser traffic source.
05
Capability planning
owner.get_launchpad_catalog · owner.preflight_project · owner.plan_launchpad
Discover live options, check readiness, and create a reviewable plan before any consequential change.
06
Confirmed operations
owner.apply_launchpad_plan · owner.get_operation
Apply an unchanged supported plan only after explicit confirmation, then recover from its durable receipt.
07
Project management
owner.create_project · owner.update_project · owner.archive_project
Create, edit, and reversibly archive projects with explicit confirmation, a reason, and an idempotency key.
Start with two read scopes; add only what an action needs.
account:read
Read the authorized account and portfolio context.
projects:read
Read projects and bounded project context within effective membership and project scope.
projects:write
Create, edit, or archive projects after explicit confirmation.
runtime:read
Read adopted runtime configuration and project web analytics.
runtime:write
Include selected runtime capabilities when creating a project and create confirmed web-analytics sources.
Two ways in. One scoped session.
01 · Browser
OAuth with PKCE
- Open Protected Resource Metadata and follow its authorization server.
- Confirm the issuer, endpoints, authorization-code grant, and
S256support. - Use an exact registered redirect URI, state, PKCE, and resource
https://povento.com/mcp. - Sign in and approve only the requested scopes and permitted account, project, environment, and capability context.
02 · Terminal or headless client
Device login
- Start a device request at
/device/authorizefor the canonical resource and requested scopes. - Open the returned verification URI and enter the displayed user code.
- Approve at
/device/approve, then poll/oauth/token. - Send the resulting bearer only to
https://povento.com/mcp; honor expiry and revocation.
Keep credentials in the client’s secure store. Never paste a bearer credential into prompts, page forms, URLs, or tool arguments. Device approval is user authorization—not a static API key.
Start with the machine-readable metadata.
These links are public documentation and discovery surfaces. They do not prove that a client is authorized. Start from Protected Resource Metadata, then use OAuth with PKCE or the device flow.