MCP Server Does Not Comply with RPC Format Issue
Thank you, but I have another issue: the MCP server does not comply with the RPC format !
Thank you, but I have another issue: the MCP server does not comply with the RPC format !
May I ask what part is not compliant? Have you encountered any error messages?
No but i had this result it's not RPC standard to communicate with other MCP client: [{"tools":[{"sl_type":"function","name":"Read_Accounts","description":"This tool for get data from salesforce","strict":false,"sl_tool_metadata":{"path":"/Ayming-DEV/04-SALESFORCE/IA Test MCP/Read_Accounts","tool_type":"pipeline"},"parameters":[{"name":"Name","type":"STRING","required":false,"description":"Le nom"},{"name":"ID_SF_18","type":"STRING","required":false,"description":"key SF"}]}]},{"Id":"0011i000001mv9yAAA","IsDeleted":false,"MasterRecordId":null,"Name":"Theo Müller S.e.c.s.","Type":"Prospect","RecordTypeId":"01258000000c5qbAAA","ParentId":null,"BillingStreet":"2 b, Rue Albert Borschette","BillingCity":"Luxembourg","BillingState":null,"BillingPostalCode":"L-1246","BillingCountry":"Luxembourg","BillingStateCode":null,"BillingCountryCode":"LU","BillingLatitude":null,"BillingLongitude":null,"BillingGeocodeAccuracy":null,"BillingAddress":{"city":"Luxembourg","country":"Luxembourg","countryCode":"LU","geocodeAccuracy":null,"latitude":null,"longitude":null,"postalCode":"L-1246","state":null,"stateCode":null,"street":"2 b, Rue Albert Borschette"},"ShippingStreet":"2 b, Rue Albert Borschette","ShippingCity":"Luxembourg","ShippingState":null,"ShippingPostalCode":"L-1246","ShippingCountry":"Luxembourg","ShippingStateCode":null,"ShippingCountryCode":"LU","ShippingLatitude":null,"ShippingLongitude":null,"ShippingGeocodeAccuracy":null,"ShippingAddress":{"city":"Luxembourg","country":"Luxembourg","countryCode":"LU","geocodeAccuracy":null,"latitude":null,"longitude":null,"postalCode":"L-1246","state":null,"stateCode":null,"street":"2 b, Rue Albert Borschette"},"Phone":"+352 266 309-10","Fax":null,"AccountNumber":null,"Website":"https://www.muellergroup.com/","PhotoUrl":"/services/images/photo/0011i000001mv9yAAA","Sic":null,"Industry":"Food & Beverage","AnnualRevenue":6000000000,"NumberOfEmployees":27500,"Ownership":null,"TickerSymbol":null,"Description":null,"Rating":null,"Site":null,"CurrencyIsoCode":"EUR","OwnerId":"00558000002llegAAA","CreatedDate":"2018-09-17T07:50:40.000+0000","CreatedById":"00558000002llegAAA","LastModifiedDate":"2025-10-31T16:35:53.000+0000","LastModifiedById":"0055q000000eFK5AAM","SystemModstamp":"2025-10-31T16:35:53.000+0000","LastActivityDate":null,"LastViewedDate":null,"LastReferencedDate":null,"IsPartner":false,"ChannelProgramName":null,"ChannelProgramLevelName":null,"Jigsaw":null,"JigsawCompanyId":null,"AccountSource":"Personal network","SicDesc":null,"Account_Affiliate__c":"GERMANY","Billing_Address_2__c":null,"Billing_County__c":null,"Billing_Region__c":null,"Data_Source_Id__c":null,"Data_Source_Name__c":null,"Do_Not_Call__c":false,"Group_Name__c":null,"Headquarters__c":true,"Industry_Code_Type__c":null,"Legal_Form__c":null,"Legal_Status__c":null,"Liquidated__c":false,"Local_Registration_Number__c":null,"Number_of_locations__c":23,"Saturn_Code__c":null,"Shipping_Address_2__c":null,"Shipping_County__c":null,"Shipping_Region__c":null,"Workforce_Band__c":"Over 5000","Industry_Number__c":null,"Origin_Details__c":null,"Origin__c":"Personal network","Year_End__c":null,"Industry_Description__c":null,"Allows_Logo_use__c":false,"Account_ID_18__c":"0011i000001mv9yAAA","Local_Registration_Number_reporting__c":null,"Category__c":null,"Trading_Name__c":null,"Additionnal_Local_ID__c":null,"BVD_Number__c":null,"Address_formula__c":"2 b, Rue Albert Borschette,L-1246,Luxembourg,,Luxembourg","X123_Cross_Sell__c":false,"Client_Report__c":"Client Report","Legal_Form_France__c":null,"Legal_form_reporting__c":null,"NAF_Code__c":null,"NAF_Label__c":null,"Workforce_Band_FR__c":"Over 5000","Workforce_Band_Reporting__c":"Over 5000 Over 5000","Cross_Sell_2018__c":false,"International_Presence__c":null,"LID__LinkedIn_Company_Id__c":null,"Group_Report__c":"Group Report","linkedin_si__Company_Profile__c":null,"KimbleOne__BillingContact__c":null,"KimbleOne__BillingParentAccount__c":null,"KimbleOne__BusinessUnitTradingEntity__c":"a1F58000005IRmNEAW","KimbleOne__BusinessUnit__c":"a1F58000005IRmNEAW","KimbleOne__Code__c":null,"Merk_description__c":null,"Merk_Data_Updated__c":false,"Merk_Last_Update_Run__c":null,"Playbooks_Next_Step_Due_Date__c":null,"KimbleOne__IsCustomer__c":false,"KimbleOne__IsSupplier__c":false,"Playbooks_Play_Info_Updated__c":null,"Playbooks_Play_Name__c":null,"Playbooks_Play_Status__c":null,"Playbooks_Step_Number__c":null,"isdc_closedate__c":null,"SageAccountReference__c":null,"Group_Name_ID_18__c":"AAA","Group_Country__c":null,"Group_State_Province_INT__c":null,"Company_creation_date__c":null,"Registered_Capital__c":null,"Other_Local_ID__c":null,"Region__c":null,"i__c":null,"Agreement_details__c":null,"iSell__OSKeyID__c":null,"KimbleOne__IsInternal__c":false,"KimbleOne__TimePatternRule__c":null,"KimbleOne__TimePattern__c":null,"decidento__Company__c":null,"decidento__Mon_compte__c":false,"Cash_on_Time_Account_Data_Source_ID__c":"0011i000001mv9y","Cash_on_Time_Score__c":null,"Cash_on_Time_Billing_Street_2__c":null,"Cash_on_Time_Billing_Street_3__c":null,"decidento__Actionnaire_principal__c":null,"decidento__Activit_compl_te__c":null,"decidento__CA_Bilan__c":null,"decidento__CA_consolide__c":null,"decidento__CA_estime__c":null,"decidento__Capital_social__c":null,"decidento__Code_NAF__c":null,"decidento__D_partement__c":null,"decidento__Date_cloture__c":null,"decidento__Date_d_immatriculation__c":null,"decidento__Effectif_consolide__c":null,"decidento__Effectif_estime__c":null,"decidento__Effectif_pr_cis__c":null,"decidento__Email_contact__c":null,"decidento__Enseigne__c":null,"decidento__Facebook__c":null,"decidento__Fonds_propres__c":null,"decidento__Forme_juridique__c":null,"decidento__Google_News__c":null,"decidento__Linkedin__c":null,"decidento__Logo__c":null,"decidento__Maps__c":null,"decidento__Nombre_actionnaires__c":null,"decidento__Nombre_de_filiales_directes__c":null,"decidento__Nombre_de_filiales_indirectes__c":null,"decidento__RCS__c":null,"decidento__R_sultat_d_exploitation__c":null,"decidento__R_sultat_net__c":null,"decidento__R_sum_activit_Decidento__c":null,"decidento__Radiate__c":false,"decidento__SIREN__c":null,"decidento__SIRET__c":null,"decidento__Scoopit__c":null,"decidento__Sigle__c":null,"decidento__TVA_intracommunautaire__c":null,"decidento__Twitter__c":null,"decidento__Type_d_tablissement__c":null,"decidento__Viadeo__c":null,"decidento__Wikipedia__c":null,"Provincial_Business_Number__c":null,"GAM_Program__c":false,"Origin_Details_List__c":"Other","Additional_Link__c":null,"Customer_ID__c":null,"Date_of_next_RFP_Tender__c":null,"Last_Year_s_Fiscal_Declaration__c":null,"Activity_Code_Type__c":null,"Activity_Code_Number__c":null,"Partnaire_actif__c":false,"Data_Quality_Description__c":"Missing: Rating,","Data_Quality_Score__c":80,"email_Public__c":null,"Fax__c":null,"Tech_nbre_de_qualif__c":0,"Company_Id_15__c":"0011i000001mv9y","KC_InvoiceShippingAddress__c":"L-1246 Luxembourg","Target_Operation__c":null,"Badge__c":null,"Shipping_Entity_Name__c":null,"isdc_closescore__c":null,"Net_Profit__c":null,"leadfeederapp__LatestWebsiteVisit__c":null,"leadfeederapp__LeadfeederLink__c":null,"leadfeederapp__WebVisitorsLink__c":null,"Activity_Description__c":null,"Nace_Code__c":null,"Nace_Description__c":null,"Industry2__c":"Food & Beverage","Holding__c":false,"Created_by_Profile__c":"CM Sales Manager","Tech_Bypass_VR__c":null,"NextActivityDate__c":null,"Created_by_Role__c":"DE DESACTIVATED USERS","DPO__c":null,"Competitor__c":false,"GDPR_Sensitive__c":false,"Tech_Company_Invoiced__c":false}]
This is the output of you server pipeline, correct? The output will be pasred to MCP required format by a component called "SnapLogic MCP adapter" running on the jcc node. The adapter handles tasks that users do not need to worry about, such as translating requests and responses. You should be able to connect to your MCP server using any popular MCP client. This demonstrates that the responses sent back by the server are fully compliant with the MCP protocol andJSON-RPC standard.