Your account, your choice of access
Add https://app.tityra.com/mcp as a remote Streamable HTTP server in an MCP client that supports OAuth. Sign in to your Tityra customer account when prompted. The permission screen identifies the connecting application and explains the access it requests.
Choose the projects this connection can use and review its permissions before allowing access. The agent can only work within those selected projects and your current account rights. If your project access is removed, the connection loses that access too.
Open Connected agents in your account menu to see each connection, its permissions and last use. Revoke a connection there to stop subsequent requests. Each agent application has its own connection.
From audit request to practical findings
Ask your agent to find an eligible project, request an audit and check its progress. Existing package, domain eligibility, authority review and delivery rules still apply. A successful request is not an instant scan or a delivery promise.
When the report is available, the agent can read its structured findings, evidence and recommendations using the permissions you granted. It can help you identify open high-priority issues and refer you back to the original finding in your workspace.
With remediation permission, your agent can record your team’s progress on a finding. A customer-reported fix remains separate from a Tityra recheck. Updates preserve the finding and report references, and conflicting edits must be refreshed before retrying.
Review payment before completing it
Give each connection a defined purpose
Permissions separate reading projects, requests, reports, findings and billing from requesting an audit, changing remediation and creating a checkout link. Read-only access does not permit changes, and a scope never grants access to another customer’s data.
For example, connect a reporting assistant with report and finding read access to one project. A separate workflow assistant can have audit-request permission for the projects you select. The consent screen shows the scopes requested by your client; decline a request if it asks for more access than you intend.
Choose the connection for your task
The authenticated account connection is for customer accounts. Partner and staff workflows are not exposed through this connection. Your MCP client must support remote Streamable HTTP, OAuth authorization code flow and PKCE S256.
For public package information and a website request review link, use https://tityra.com/mcp without signing in. That public server does not access accounts or reports. The two server URLs have different capabilities and authentication requirements.
Connecting an agent does not keep it running in the background. Your client controls when it checks progress. This first version supports status queries and user-completed checkout; automatic spending and persistent background monitoring are not included.
