PortalFirma

MCP · Claude

Claude / Connectors Directory

Claude descubre OAuth solo vía MCP. El authorize/login corre en api-integration; el resource es api-mcp. El listing público se envía en Organization settings → Directory.

Redirect URI fijo de Claude: https://claude.ai/api/mcp/auth_callback

Issuer (register / authorize / token): https://integracion.portalfirma.cl

Claude.ai cloud requiere HTTPS público en el MCP y en el issuer. No uses hosts locales desde el conector en la nube.

1. Registrar cliente

DCR contra api-integration, no contra api.

DCR
curl -X POST https://integracion.portalfirma.cl/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Claude",
    "redirect_uris": ["https://claude.ai/api/mcp/auth_callback"]
  }'

2. Flujo esperado

  1. 1. Claude conecta a la URL MCP (api-mcp).
  2. 2. Recibe 401 + resource_metadata.
  3. 3. Descubre issuer = api-integration y abre /oauth/authorize.
  4. 4. Partner inicia sesión y autoriza.
  5. 5. Claude intercambia code por access_token en /oauth/token.
  6. 6. tools/list y tools/call con Bearer hacia api-mcp.

3. Connectors Directory

Probar el conector no requiere listing: en Claude.ai ve a Customize → Connectors → Add custom connector e ingresa https://mcp.portalfirma.cl/api/mcp.

Para aparecer en el catálogo público hace falta una org Team o Enterprise y envío en Organization settings → Directory. Docs de Anthropic: submission, review criteria.

Privacy policy pública: /mcp/privacy.

4. Ficha para el portal

Copia estos campos al submission portal. El slug queda fijo al publicar.

Server URL
https://mcp.portalfirma.cl/api/mcp
Transport
Streamable HTTP
Connection
Universal URL
Authentication
OAuth 2.0 with Dynamic Client Registration (PKCE S256)
Name (max 100)
PortalFirma
URL slug (permanent)
portalfirma
Tagline (max 55)
E-sign, notary, and document workflows in Chile
Categories
Productivity, Business, Legal
Documentation URL
https://developers.portalfirma.cl/mcp
Privacy policy URL
https://developers.portalfirma.cl/mcp/privacy
Support contact
contacto@portalfirma.cl
Company
PortalFirma
Company website
https://www.portalfirma.cl
Data handling
Read and write
Description (max 2,000)
PortalFirma is a Chilean electronic signature and virtual notary platform. This connector lets a signed-in PortalFirma partner ingest documents, extract signers, send files to e-sign, look up operations by RUT or phone, resend signature links, search uploaded document content, find notary templates, and check wallet credit.

The server talks only to PortalFirma first-party APIs. Each session is scoped to the authenticated company. Sending to sign, notifications, CDS signing, and wallet top-ups may involve PortalFirma certificadoras, email or WhatsApp delivery, and Flow checkout when the user starts those actions.

Connect the remote MCP URL, complete OAuth login with a PortalFirma partner account, and grant access. Documentation: https://developers.portalfirma.cl/mcp
Primary use cases
Enviar un documento a firma: «Te adjunté el mandato.pdf. Ingéstalo, extrae los firmantes y envíalo a firmar. El pagador es pagos@miempresa.cl.»
Consultar una operación: «Muéstrame el detalle de la operación 482910 y dime quién falta por firmar.»
Reenviar un link de firma: «Reenvía el link de firma al firmante de la operación 482910 que aún no ha firmado.»
Buscar en un documento: «En el PDF que acabo de subir, ¿qué dice sobre el plazo de vigencia?»
Buscar una plantilla notarial: «Busca plantillas de mandato especial, dime los campos y complétala para enviarla a firmar.»
Connection requirements
Requires a PortalFirma partner/company account. The user must sign in with email and password on the OAuth page (integracion.portalfirma.cl). A personal account without company access cannot connect.

Read / write capabilities: Read and write. No uses Read only.

Test setup instructions
PortalFirma MCP (production)

MCP URL: https://mcp.portalfirma.cl/api/mcp
Transport: Streamable HTTP
OAuth: Dynamic Client Registration (RFC 7591) + PKCE S256
Authorization server: https://integracion.portalfirma.cl
Docs: https://developers.portalfirma.cl/mcp
Tool catalog: https://developers.portalfirma.cl/mcp/tools
Privacy: https://developers.portalfirma.cl/mcp/privacy

1. In Claude, add the connector (directory listing or Customize → Connectors → Add custom connector) with URL https://mcp.portalfirma.cl/api/mcp
2. When prompted, complete OAuth. Claude registers itself via POST https://integracion.portalfirma.cl/oauth/register (no pre-issued client_id). Redirect URI: https://claude.ai/api/mcp/auth_callback
3. Sign in with the test partner account:
   Email: REPLACE_ME_EMAIL
   Password: REPLACE_ME_PASSWORD
   Language: the authorize page is in Spanish. Use “Iniciar sesión”, then allow access.
4. After grant, tools/list should return the full catalog scoped to this company.

Test partner is a fully populated company account. Suggested prompts (replace IDs if needed):

- Session: “What PortalFirma partner am I authenticated as?”
- Templates: “Search notary templates for mandato especial, show me the form groups, then send it to sign with the field values I give you.”
- Operations lookup: “List signing operations for RUT REPLACE_ME_RUT between REPLACE_ME_START_DATE and REPLACE_ME_END_DATE, limit 10.”
- Process detail: “Show process detail for operation REPLACE_ME_OPERATION.”
- Ingest + extract (attach a small PDF): “Ingest this PDF, extract the signers, and tell me missing_fields.”
- Search: after ingest, “In that document, what does it say about plazo de vigencia?”
- Wallet: “What is my PortalFirma wallet balance?” Do not complete a Flow payment.
- Manage signing: “Resend the signature link to the unsigned signer on operation REPLACE_ME_OPERATION.”
- CDS: “List pending CDS documents for RUT REPLACE_ME_RUT.” Do not call request_sign_code / sign_documents (certificate password + SMS).

Do not use CDS certificate passwords, 2FA codes, or live card payments. Contact: contacto@portalfirma.cl

Upload the PortalFirma mark (square PNG/SVG). Source: https://developers.portalfirma.cl/icon.svg