MCP server · PPL
ppl-nextgen
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
⚠ Proposed MCP surface. No official hosted MCP server was found for PPL. The tools below are a candidate set derived from this provider's API, and the link points at the source descriptor rather than a live server. If PPL publishes an official server, this page will update to it on the next build.
Descriptor
Candidate descriptor · transport http
Tools
placements_placement_get_all— Returns a list of Placement records and any Programme structures, based upon various query parameters. This end point will also provide minimal information about any Contracts within the Placement structure. Pagination fplacements_placement_post— Creates a Placement record. This is the starting point in order for Contracts and Programmes to be added into the platform.placements_placement_get_by_id— Returns the Placement structure for a specified Placement record. This will contains information about the Placement, its Programmes and summarised information about Contract records within the Placement structure.placements_placement_put— Updates a Placement record, where the record is in a state that enables its update.placements_placement_delete— Deletes a Placement record, where the record is in a state that enables its deletion.placements_programme_post— Creates a Programme record under the Placement structure. This enables the grouping of Contract records that address a common insurance purpose. Contracts can be added at the time of creation.placements_programme_get_by_id— Returns the Programme structure for a specified Programme record. This will return information about the Programme and summarised information about Contract records within the Programme structure.placements_programme_put— Updates a Programme record. Contracts can be added into the Programme structure.placements_programme_delete— Deletes a Programme record, where the record is in a state that enables its deletion. Any Contract records that exist in this Programme will be moved into the default Programme.placements_contract_get_all— Returns a list of Contract records, based upon various query parameters. Pagination functionality is supported on this operation.placements_contract_post— Creates a Contract record under the Placement structure. This will also create the "default" Section of information, which is necessary for adding Underwriters and Facility markets for underwriting purposes.placements_contract_get_by_id— Returns a single Contract record. This record will contain core Contract information, that includes data attributes that summarise information about the risk to be insured, as well as a summarised list of any Contract Seplacements_contract_put— Updates the Contract record. This will also update the "default" Section of information.placements_contract_delete— Deletes a Contract record, where the record is in a state that enables its deletion.placements_section_get_all— Returns a list of Section records, within a single Contract record. This returned list is a subset of all Section record fields, based upon various query parameters.placements_section_post— Creates a Section record under the Contract, representing a specific partition of the overall risk and / or coverage to be insured.placements_section_get_by_id— Returns a single Section record. This record will contain all the Section-related structured data.placements_section_put— Updates a Section record, where the record is in a state that enables its update.placements_section_delete— Deletes a Section record, where the record is in a state that enables its deletion.placements_participation_get_all— Returns a list of Participation records, within a single Section. This returned list is based upon various query parameters. Pagination functionality is supported on this operation.placements_participation_post— Creates Participation records representing either a single Open Market Underwriter and the Carrier Stamps they are permitted to use, or a multiple of Participation records representing each Underwriter from a panel of unplacements_participation_get_by_id— Returns a single Participation record. This record will contain the underwriter attributes for underwriting a risk, as well as any facility panel information, where the Underwriter's involvement is made through a Masplacements_participation_put— Updates a Participation record, where the record is in a state that enables its update. Where an Underwriter update involves an update upon a Facility Panel, all involved Participations of said Facility Panel will be updplacements_participation_delete— Deletes a Participation record, where the record is in a state that enables its deletion.placements_negotiation_get_all— Returns a list of all Negotiation records based upon various query parameters. Pagination functionality is supported on this operation.placements_negotiation_post— Creates a single Negotiation record in response to an Underwriter User's response. Broker Users will be able to accept or reject, confirm or negotiate on various attributes of their involvement, i.e. acceptance of coplacements_negotiation_get_by_id— Returns a single Negotiation record. This record will contain attributes pertaining to the single negotiation position between a Broker User and an Underwriter User, based upon its negotiation status within the insuranceplacements_negotiation_put— Updates a Negotiation record, where the record is in a state that enables its update. For example, where Negotiations are in a saved and unsent state.placements_negotiation_send— Initiates the operation to send the latest negotiation response back to an Underwriter. The outcome of this will either (1) agree to the change of terms; (2) negotiate the Underwriter's latest offer; or (3) withdrawplacements_contract_assign_roles— Initiates the asynchronous operation to assign the contractual roles to Participations and their Stamps on the Contract. Where a specific Slip Leader has been identified, the process will take this into consideration dursubmissions_negotiation_get_all— Returns a list of all Negotiation records based upon various query parameters. Pagination functionality is supported on this operation.submissions_negotiation_post— Creates a single Negotiation record in response to a Broker User's request for consideration. Underwriter Users will be able to reject, confirm or negotiate on various attributes of their involvement, i.e. acceptancesubmissions_negotiation_get_by_id— Returns a single Negotiation record. This record will contain attributes pertaining to the single negotiation position between an Underwriter User and an Broker User, based upon its negotiation status within the insurancsubmissions_negotiation_put— Updates a Negotiation record, where the record is in a state that enables its update. For example, where Negotiations are in a saved and unsent state.submissions_negotiation_reassign— Reassigns a Negotiation record to another Underwriter User. The destined Underwriter User does not have to be a member of the same Carrier Team owning the original Submission, but must exist within the same Company hierasubmissions_submission_get_all— Returns a list of all Submission records based upon various query parameters. Pagination functionality is supported on this operation.submissions_submission_get_by_id— Returns a single Submission record. This record includes structured data pertaining to a single Contract offering (and any subsequent Sections, if applicable) as well as references to download (1) the Market Reform Contrsubmissions_submission_send— Initiates the operation to send the latest Underwriter responses as part of a response to a Submission back to the Broker. The outcome of each Negotiation will either (1) agree unconditionally to the terms; (2) conditionorganisations_broker_organisations— This end point returns a list of both Broker Teams and Team Members for which the requestor is a member of. This is required in order to support the creation and management of Placements, Programmes and Contract recordsorganisations_carrier_organisations— This end point returns a list of both Carrier Teams and Team Members for which the requestor is a member of. This is required in order to support the management of Submissions and Negotiation records in the platform, asorganisations_broker_markets_facilities— Returns a list of Master Facility markets on the platform that the Broker Team has been authorised to utilise on a Contract and /or Section.organisations_broker_markets_underwriters— Returns a list of Carrier Company firms and its Underwriters that a Broker Team is authorised to engage with for insurance placement purposes.organisations_broker_markets_stamps— Returns a list of Carrier Stamps that (i) a specified Underwriter has the authority to underwrite risks with; and (ii) that a Broker Team is authorised to engage with.documents_document_get_all— Returns a list of all Document records associated within a specified Placement structure, based upon various query parameters. Pagination functionality is supported on this operation.documents_document_post— Creates a Document record, representing either the Market Reform Contract (MRC) or another type of supporting document. The request contains the document attributes as well as the electronic file which will be submitteddocuments_document_get_by_id— Returns a single Document record. This record will contain the document attributes of the document, but does not provide the electronic file.documents_document_put— Updates the data attributes of a Document record. This operation will not replace the electronic file.documents_document_delete— Deletes a Document record, where the record is in a state that enables its deletion.documents_document_get_content— Returns the electronic file that is represented by the Document record. This is the subsequent end point that is called following an asynchronous response that the electronic file is ready to be downloaded.documents_document_post_download— Initiates the asynchronous operation to download the electronic file of this document.documents_document_get_security_content— Returns the electronic file that represents the Market Reform Contract with its underwriting security page(s) and settlement information. This is the subsequent end point that is called following an asynchronous responsedocuments_document_post_security_download— Initiates the asynchronous operation to download the Market Reform Contract with its underwriting security page(s) and settlement information.events_notification_get_all— Returns a list of all Notification records, based upon various query parameters. Pagination functionality is supported on this operation.events_notification_get_by_id— Returns a single Notification record. This record will contain attributes pertaining to the type of notification and any type of action that is required. The context information is the subject of the notification.events_notification_mark_all_as_read— Initiates the operation to update all non-technical Notification records as read from a defined date.events_transaction_get_all— Returns a list of all Transaction records, based upon various query parameters. Pagination functionality is supported on this operation.events_transaction_get_by_id— Returns a single Transaction record. This record will contain attributes pertaining to the category and type of transaction. The content is determined upon the type of the transaction.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.